Data · Integrations & data sources
Best practices for sending events
How to send the events your own systems produce so that flows start on time, conditions match and segments stay reliable: timing, dates, one event per change, values, event types, a reminder pattern and the common mistakes with what each one costs.
Events are what make a flow move: a payment starts a thank-you message, a booking starts a reminder, a cancellation stops it. When your own systems send those events, through the API, a webhook or an automation platform such as Zapier or Make, how they send them decides whether the flow reacts. An event that arrives late, with a date missing its time, or with a value spelled differently from the one the flow expects is still stored on the contact, but the flow ignores it and nothing tells you so. This page collects the habits that avoid that, and what each mistake costs.
Send every event as it happens
The rule that matters most: send every event as soon as it happens, and never more than 30 minutes after.
Flows react to events that are happening now. Instasent compares the event's date with the moment it arrives, and an event that is too old, or dated in the future, never starts a flow. Nothing is lost: the event is stored on the contact's profile and can be used in segments and reports. It simply doesn't trigger anything. The same applies when the event should end a flow, advance a Wait for activity or count as a goal: a cancellation that arrives late doesn't stop a flow that is already running.
Sending in small groups is fine as long as each group goes out within seconds or a few minutes of the events in it. What doesn't work is collecting the day's events and sending them once an hour or once a night: by then every event is late.
Loading history is a different job, and it never starts flows: the first sync of a newly connected source, CSV imports and manual imports. Which events can start a flow, and the safeguards behind this rule, are explained in The trigger: who enters and when and Limits and safeguards.
Give each event a full date, or none
An event's date says when it happened. It needs a time and a time zone, for example
2026-11-12T17:42:00+01:00.
- A date without a time (
2026-11-12) is stored as midnight. It almost never falls close enough to the moment it arrives, so the flow silently doesn't start. - No date at all means "now". For events sent in real time, that is the simplest and safest option.
- The moment it happened, not the moment it's planned for. When someone books a meeting for next Tuesday, the booking happened today; Tuesday is a detail of the event, not its date.
One event per change
An event is a fact that happened once, and it can't be edited afterwards. When something changes, a meeting is cancelled or a payment is refunded, the right move is to send a new event describing the new state, never to resend the old one: an event sent again with the same identifier is rejected, and the change is lost.
To keep the story readable, each event carries the identifier of the thing it is about, the meeting, the payment or the order, and that identifier stays the same across all its events. That way the booking, the cancellation and the new booking of the same meeting can be followed on the contact's timeline.
Every event belongs to a contact
Each event has to say which contact it belongs to, with the same identifier your systems use for that person when they send contacts. An event that can't be tied to a contact can't be used by flows or segments.
Values a flow can use
Flows and segments filter on the details an event carries, such as a meeting's status or a payment's method. Those filters only work when the values are consistent:
- No placeholder values. "#none", an empty value, "-", "N/A" or "null" all count as no value. It is better to leave the detail out.
- One vocabulary, always. A status must be written the same way every time: "attended" every day, never "attended" one day and "Asistió" the next. A flow condition matches one spelling only.
- Short lists are what flows filter on. Statuses, categories, types and yes/no values are what conditions and branches use. Free text and identifiers are useful on the timeline, but not for filtering.
Choose the right event type
Instasent has a catalog of event types: payments, orders, checkouts, meetings, deals, leads, appointments and more. A catalog type comes with details the dashboard and flows already understand, so it is always the first choice.
- Action performed carries a free action name, such as
meeting_reminder, and can start a flow. It suits moments your own system decides, like a reminder. - Custom event is for something no catalog type describes. It can start a flow too.
- Generic event and Metric / Analytics never start a flow. They are fine for reports, not for anything a flow should react to.
Pattern: a reminder before a meeting
A flow can wait a fixed time after something happens, from 1 minute to 90 days, but it can't wait until a date written inside an event, such as "24 hours before the meeting". A Wait for activity step also counts only events that happen after the wait started. Scheduled triggers in flows are coming soon; until then, the reminder moment comes from your system:
The booking
When the meeting is booked, your system sends Meeting registered with the meeting's identifier and date. If a booking fits your business better as an appointment, Appointment is the type for the booking itself.
The reminder
At the exact moment the reminder must go out, for example 24 hours before the meeting, your system sends Action performed with the action
meeting_reminder. The flow starts on Action performed with the condition action equalsmeeting_reminderand sends the message right away.The cancellation
Meeting canceled is added to the flow as an exit event, so a cancellation stops a run that is still in progress. How exit events work is explained in Goals and exits.
Rescheduling is three events: Meeting canceled for the old meeting, a new Meeting registered for the new date, and the reminder sent at the new time. Your system also needs to stop sending the reminder planned for the old date, since Instasent can't know it no longer applies.
Common mistakes and what they cost
| Mistake | What it costs |
|---|---|
| Sending events in hourly or nightly batches | They are stored, but none of them start a flow: the messages are never sent |
| A date without a time | It reads as midnight, and the flow doesn't start |
| A date without a time zone | It reads at the wrong hour, and the flow may not start |
| Dating an event on the day something is planned for | A date in the future: nothing starts |
| Resending an event to update it | It is rejected and the change is lost; the flow never learns of it |
| A late cancellation | The flow in progress isn't stopped, and the contact may receive a reminder for a meeting that no longer exists |
| Placeholder values such as "N/A" or "-" | They count as empty, so conditions on that detail don't match |
| The same status written in several ways | The flow reacts to some contacts and not others |
| Using Generic event or Metric / Analytics for something a flow needs | The event never starts a flow |
| Expecting a CSV import or a first sync to start flows | Nothing starts, by design; send a campaign to reach those contacts once |
The developer side of these rules, with the exact formats, is in Ingest API best practices.
Related
- API & webhooks: the source, its credentials and the shape of what it receives.
- The trigger: who enters and when: which events can start a flow.
- Limits and safeguards: the events that never start a flow and why.
- Goals and exits: how exit events and goals end a run.
Last updated