CRM build for the freelancers.
Moxie currently provides 22 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Client Created
Triggered when a new client is created.
Client Updated
Triggered when an existing client is updated.
Client Deleted
Triggered when an existing client is deleted.
Project Created
Triggered when a new project is created.
Project Updated
Triggered when an existing project is updated.
Project Completed
Triggered when an existing project is completed.
Task Created
Triggered when a new task is created.
Task Updated
Triggered when an existing task is updated.
Task Deleted
Triggered when an existing task is deleted.
Client Task Approval
Triggered when a task is moved to client approval.
Form Submitted
Triggered when a new form is submitted.
Time Entry Created
Triggered when a new time entry is created.
Time Entry Updated
Triggered when an existing time entry is updated.
Time Entry Deleted
Triggered when an existing time entry is deleted.
Meeting Scheduled
Triggered when a new meeting is scheduled.
Meeting Updated
Triggered when an existing meeting is updated.
Meeting Cancelled
Triggered when a meeting is cancelled.
Opportunity Created
Triggered when a new pipeline opportunity is created.
Opportunity Updated
Triggered when an existing opportunity is updated.
Opportunity Deleted
Triggered when an existing pipeline opportunity is deleted.
Invoice Sent
Triggered when an invoice is sent.
Payment Received
Triggered when a payment is received.
Create a Client
Create a new client record in moxie CRM.
Create a Task
Create a task in project.
Create a Project
Creates a new project in moxie CRM.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Moxie event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Client Created
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Moxie action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create a Client
Combine Moxie with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
Client Created
Finishes with
Create a Client, then preserve the outcome in Coherence
The exact authentication fields depend on Moxie. The workflow structure stays straightforward:
Authorize the Moxie account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Moxie or provide a complementary trigger or action.
Moxie currently provides 22 triggers that can start a workflow and 4 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Moxie currently lists 22 triggers and 4 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Moxie triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
