Oneflow Triggers (Zapier)

A Zapier trigger is an event that starts an automated workflow, called a "Zap." A trigger is based on an event, such as a new email in your inbox or a new form submission. When a trigger activates, Zapier automatically performs a series of actions (called "steps") in response.

How to set up the trigger

In your Zapier account, click Create Zap.
In the Trigger section, search for and select Oneflow.
For the Trigger event, select Contract Status Changed and click Continue.
Select your Oneflow account. If you haven't connected it, follow the prompts to sign in and authorize Zapier. Click Continue.
In the Configure step, select the contract status that will activate your Zap.

Configure the trigger status

In the Trigger when contract status changed to field, choose one or more statuses from the dropdown menu.

Available trigger statuses

You can use the following Oneflow contract statuses as a trigger:

Sent

Activates the trigger when you send a contract.

Signed

Activates the trigger when all participants have signed the contract.

Declined

Activates the trigger if a participant declines the contract.

Expired

Activates the trigger if the contract passes its expiration date without being signed or declined.

Deleted

Activates the trigger when you delete the contract.

Draft contract approved

Activates the trigger when a contract completes the internal approval process (all internal approvers have approved the contract) in Oneflow.

When to use this trigger:

Use the "Draft contract approved" trigger to automate the next steps in your contract lifecycle immediately following internal review. This ensures a seamless hand-off from your legal or management team to the next stage of the workflow.

EXAMPLE SCENARIOS

Notify the contract owner: Send a customized email or a direct message in Slack/Microsoft Teams to the contract owner, informing them that all internal approvers have approved the contract and it is ready to be sent.
Update CRM status: Automatically update a deal stage in your CRM (e.g., from "Internal Review" to "Ready to Send") to keep your sales pipeline accurate.
Create a task for the next step: Generate a task in a project management tool, assigning the contract owner to send the approved contract to the external participants.

Using multiple triggers

You can select multiple statuses in the Trigger when contract status changed to field. This allows a single Zap to run for different status changes. For example, you could select both 'Signed' and 'Declined' to trigger a Zap that updates your CRM system in both cases.

Trigger output

When the Oneflow trigger runs, it provides the Contract ID as an output. You can use this ID in subsequent steps of your Zap, for example, to fetch more details about the contract.

You can read more about Oneflow contract statuses in our developer documentation.