Deleting a campaign event permanently removes it from a campaign schedule. Once deleted, an event cannot be restored and must be recreated if you need it again. Deleting only affects future executions—events that already ran are not reversed. Use deletion when an event was created by mistake, is no longer relevant, or you are restructuring your campaign timeline.

Editing a campaign event lets you adjust when it runs (before/after a reference date), what it does (send a message or start a flow), and how it behaves if a contact is already in an active flow. This is useful when you need to refine timing, swap the targeted flow/message, or switch to a different Date & Time reference field. Edits apply only to future executions—messages or flows that already ran are not changed retroactively.

Exporting campaigns lets you download campaign configurations and any related flows as a JSON file. This is useful for backup, moving campaigns between workspaces, sharing campaign logic with another team, or reusing a campaign in a different environment. Exporting does not change or remove campaigns from your workspace.

Activating an archived campaign lets you resume it without recreating anything. Once active again, the campaign will send messages or start flows using its existing events and settings. Reactivation only affects future executions and does not replay messages or flows that were missed while the campaign was archived.

You can edit a campaign to update its basic properties—mainly the campaign name and the single contact group it targets. These changes apply going forward: existing campaign events remain configured, but switching the group changes which contacts are eligible to receive future campaign events.

Archiving a campaign pauses it without deleting it. An archived campaign stops sending messages or starting flows, but its events and settings remain saved so you can review or reactivate it later. Archiving only affects future executions—anything that already ran is not reversed.

Campaign events can trigger while a contact is already active in a flow. Sending priority options let you decide whether the campaign event should interrupt that flow, be skipped, or run alongside it—so you can protect important conversations or force delivery when the campaign action must take precedence.

Campaign events run relative to a Date & Time value stored on a contact. While built-in fields such as Created On can be used, many use cases require a custom Date & Time contact field—such as the moment a contact joins a group or completes a flow. This guide shows how to create a custom field in a flow, populate it automatically with the current date and time, convert the field type to Date & Time, and then use it in a campaign event.

A campaign allows you to send messages or start flows for contacts relative to a date, but only for contacts belonging to one specific contact group. Each campaign has a name, operates on one contact group, and contains one or more campaign events. This guide explains how to create a campaign and prepare it for adding events.

A campaign event defines an action that runs at a specific time relative to a Date & Time value on each contact—such as Created On, or a custom Date & Time field like an appointment or due date. Events can either send a message or start a flow, and a single campaign can include multiple events. In this guide, you’ll learn how to open an existing campaign, create a new event, choose the event action, configure the timing offset (before/after, amount, reference field, delivery time), and save the event so it appears in the campaign schedule.