LoopfourStart a workflow when another system changes
See which connected systems can start a workflow, such as a deal changing stage in your CRM or a payment arriving, and how to set one up.
At the end of this page your workflow will start when something changes in another system, such as a deal closing in HubSpot or a payment settling in Airwallex.
Which systems can start a workflow
| System | Example events in the Event list |
|---|---|
| HubSpot | Deal: Creation, Deal: Property Change, Company: Creation, Contact: Creation, Quote: Creation, Quote: Property Change |
| Airwallex | Payment Attempt Paid, Payment Attempt Settled, Deposit Pending, Deposit Settled |
| Slack | A new message, someone mentioning the app, a reaction, a file shared |
HubSpot also offers creation, change, merge, restore and deletion events for tickets and conversations.
These are the systems you can pick as a trigger in the editor. Other connected systems can still be read and updated by a workflow's steps. Your developer can set up other ways to start a workflow from outside Loopfour.
Before you start
- Connect the system under Integrations. See Connect a system.
- Open the workflow in the editor.
Set up the trigger
Drag the system into Triggers
In the block list, open Triggers and drag HubSpot, Airwallex or Slack onto the canvas. It replaces the current trigger.
Choose the account
Choose the trigger block. For HubSpot pick the HubSpot Account; for Slack pick the Slack Workspace.
Choose the event
Pick the change that should start the workflow from Event.
For a HubSpot Property Change event, also type the HubSpot field to watch under Property Name, such as the deal stage. For Slack message events, Keywords limits runs to messages that contain words such as "invoice" or "refund".
Deploy
Press Deploy. Events start the workflow only while it is Active.
Narrow it down
A property change event fires for every change to that field. To act only on one value, such as a deal moving to "Closed won", add a decision step straight after the trigger. See Make a decision.
Each trigger also has an advanced filter box for your developer, such as Filter (JSON) or Advanced JSON filter (optional). Leave it empty unless your developer sets it.
Check it worked
- Make the change in the other system, such as moving a test deal to a new stage.
- The run appears under Runs.
If something goes wrong
- No run appeared. Check the workflow is Active, the right account is chosen, and the event matches. See A workflow did not run.
- The connection stopped working. See A connection stopped working.
Related
Start a workflow when an email arrives
Use the inbound email address of a workflow so vendor bills or remittances sent to it start a run, with the email and attachments as input.
Use results from earlier steps
Reuse a value from an earlier step, such as an invoice number or an amount, in a later step, much like a mail-merge field in a letter.