Suppression

EzFlow tracks opt-outs at two levels — a per-contact unsubscribed flag and a workspace-level suppression list — so you can be confident that messages are never delivered to contacts who should not receive them.

The unsubscribed flag

Every Contact has an unsubscribed boolean. When it is true, the contact is excluded from Broadcast sends automatically — no configuration required.

The flag is set in three ways:

UNSUBSCRIBE_CONTACT node — use this inside a Workflow to programmatically opt out a contact. Pass the contact id and an optional reason. See UNSUBSCRIBE_CONTACT.
Admin suppression — suppressing a contact via the UI sets unsubscribed to true and records a suppressionReason and suppressedAt timestamp on the contact record.
Batch import — contacts can be imported with unsubscribed: true to respect pre-existing opt-outs.

The suppression list

The suppression list is a workspace-level blocklist of email addresses and phone numbers that are excluded from communication regardless of which contact record they belong to. Each entry records:

The blocked email or phone (at least one required per entry)
A reason string
An optional source (e.g. the origin of the opt-out)
An optional expiry date — if set, the entry is no longer active after that date

You can view and manage suppression list entries at Marketing → Suppression (or from the Contacts area).

Checking suppression in a Workflow

Use the CHECK_SUPPRESSION node to query the suppression list for a specific email or phone before sending. The node returns a suppressed boolean that you can route through a CONDITIONAL node to branch your Workflow:

suppressed: true — skip the send or log an activity
suppressed: false — proceed to the send node

This is the recommended pattern for any Workflow that sends a message to a user-supplied address and needs to respect the suppression list before dispatching.

How Broadcasts handle suppression

When a Broadcast runs, EzFlow automatically filters the resolved audience to contacts where unsubscribed is false. Contacts who have been unsubscribed — whether by UNSUBSCRIBE_CONTACT, admin action, or import — never receive the message.

Compliance angle

Keeping unsubscribes and suppressions accurate helps you honor opt-out requests and satisfy messaging regulations. EzFlow makes it easy to capture opt-outs from inbound triggers (webhook, form), propagate them through a Workflow via UNSUBSCRIBE_CONTACT, and have the change take effect automatically on every future Broadcast send.

Contacts — the per-contact unsubscribed flag
Broadcasts — how suppression is enforced at send time
CHECK_SUPPRESSION node — query the suppression list in a Workflow
UNSUBSCRIBE_CONTACT node — mark a contact as opted out