Custom events and API-triggered workflows

You can now send events into Conversion from your product, your billing system, or a script, and trigger a workflow on them. The same events are available to segmentation and to Liquid, so a signal that starts a run can also personalize what the run sends.

Custom events

Events arrive through a batch upsert endpoint and appear as engagements on the contact timeline. Payloads support JSON dot notation, so a nested field in the event body can be referenced directly in a statement.

API trigger workflows

A workflow can start from an API call rather than only from a contact-side event. The trigger context is exposed to Liquid inside the workflow, which makes the data that started the run available to every step in it.

CSV Uploads v2

CSV import was rebuilt. Batches run in parallel, the job sends heartbeats so a long import no longer looks stalled, and column headers are detected rather than assumed.

Improvements

• Automations New workflow nodes for creating a task, assigning to a queue, and linking to a campaign.
• Automations A validation endpoint catches broken configuration before a workflow goes live.
• Data Model Contact variable change events fire on update, so a workflow can react to a field changing instead of polling for it.
• Email A recipient allowlist restricts who a workspace can send to, which is what teams want while testing.
• Admin OAuth errors for Salesforce and Slack surface what went wrong instead of failing quietly.
• Admin Default views are configurable per workspace.