Per-pair page

Connect Iterable to Notion in two minutes.

Real-time triggers from Iterable, ready-made actions in Notion. Filter, transform, and route without writing a line of code.

Connect Iterable to Notion — start free See reverse direction

Trigger app

Iterable as the trigger

Workflows fire when something happens in Iterable.

Iterable has no triggers yet. Use the catalog's universal Webhook trigger as the upstream.

Action app

Notion as the action

Workflows do something in Notion, instantly.

See all 12 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Iterable → Notion

When something happens in Iterable, do it in Notion.

0 Iterable triggers wired to 12 Notion actions.

Notion → Iterable

Or fire it the other way around.

3 Notion triggers wired to 6 Iterable actions downstream.

See Notion → Iterable →

How it works

Connect Iterable and Notion in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Iterable and Notion
Open TinyCommand, authorize Iterable and Notion once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Iterable trigger
Drop the Iterable → New event trigger onto the canvas. TinyCommand auto-registers the webhook.
POST /v1/webhooks/iterable.event
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Notion action
Drop the Notion → Append Content action below it. Map fields from the Iterable payload into the Notion inputs.
notion.append-blocks
5
Publish
Publish and forget
Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Iterable + Notion.

How long does it take to connect Iterable and Notion on TinyCommand?

Under two minutes. Authorize Iterable and Notion once each, drop the Iterable trigger and Notion action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Iterable ↔ Notion integration real-time?

Yes. Both Iterable and Notion expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between Iterable and Notion?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Notion.

What Iterable events can trigger a Notion workflow?

Use TinyCommand's universal Webhook trigger to receive Iterable events, then run any of the 12 Notion actions downstream.

Do I need a paid plan to use Iterable with Notion?

No. There's a free tier that covers most Iterable+Notion use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Notion → Iterable instead?

Build it the same way, in reverse. There's a dedicated /integrations/notion/with/iterable page with the reverse-direction triggers and actions.