How do I trigger a Campaign Monitor journey with a custom event from a Flow?
The Send Event to Campaign Monitor action lets a Salesforce Flow send a custom event, such as purchased or registered, to a Campaign Monitor subscriber. If a journey in Campaign Monitor is triggered by that event name, the subscriber enters the journey.
The action is one of our invocable actions and is included on our Enterprise plan.
Setting Up the Action
Add the action to a record-triggered flow on an object that has an email field, such as Contact or Lead. You'll find it under the Campaign Monitor category in Flow Builder. Then fill in the following:
• Salesforce Email Field: the email field on the triggering record that identifies the subscriber in Campaign Monitor.
• Campaign Monitor Client: the client the event is sent to.
• Event Name: the name your journey listens for. Use 2 to 30 letters, numbers or underscores, for example item_purchased. You can also use a flow resource such as {!EventName}.
• Event Property (optional): a name and value sent with the event, for example lead_source and {!$Record.LeadSource}. You can use the property to personalize your journey emails.
Note: Developers calling the action from Apex can send several properties at once by passing JSON in the Event Data input, for example {"Item":"Chocolate","Price":"12.95"}.
Setting Up the Journey in Campaign Monitor
In Campaign Monitor, create a journey that is triggered by the event, using the same event name as your flow. A new event name shows up in Campaign Monitor once it has been sent for the first time. Learn more about journey triggers.
When the Event Is Sent
You can put the action on the flow's immediate path. The record has just been saved, so we send the event from a background job straight after the save. Bulk updates such as data imports are supported, and events beyond Salesforce's callout limit are sent in a follow-up job.
If an event doesn't arrive, check that the record has a value in the selected email field, because records without an email are skipped. Also check that the event name matches the journey trigger exactly. Any errors from Campaign Monitor are logged in maintenance.
Related Articles
• Invocable Actions [Full Guide]
In this answer
Need a hand?Find an answer, or talk to someone who can help.
Ask Campaign Monitor assistantContact the team →