Per-pair page

Connect Copper to Notion in two minutes.

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

Connect Copper and Notion See reverse direction

Trigger app

Copper as the trigger

Workflows fire when something happens in Copper.

See all 10 triggers →

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.

Copper → Notion

When something happens in Copper, do it in Notion.

10 Copper triggers wired to 12 Notion actions. Most-used pairing: Company Created → Append Content.

Notion → Copper

Or fire it the other way around.

3 Notion triggers wired to 6 Copper actions downstream.

See Notion → Copper →

Popular pairings

Common Copper → Notion workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 120 combinations

When company created in Copper, append content in Notion.

Fires when a new company is created in the Copper CRM. Useful for "auto-enrich firmographic data via Clearbit/Apollo" workflows that augment the company record right after creation.

When company created in Copper, create database in Notion.

Fires when a new company is created in the Copper CRM. Useful for "auto-enrich firmographic data via Clearbit/Apollo" workflows that augment the company record right after creation.

When company created in Copper, create page in Notion.

Fires when a new company is created in the Copper CRM. Useful for "auto-enrich firmographic data via Clearbit/Apollo" workflows that augment the company record right after creation.

When company created in Copper, delete block in Notion.

Fires when a new company is created in the Copper CRM. Useful for "auto-enrich firmographic data via Clearbit/Apollo" workflows that augment the company record right after creation.

When company updated in Copper, append content in Notion.

Fires on any change to a company record — field edits, custom-field updates, owner reassignments. For specific transitions (e.g., status moved to Customer), filter the payload by changed-field.

When company updated in Copper, create database in Notion.

Fires on any change to a company record — field edits, custom-field updates, owner reassignments. For specific transitions (e.g., status moved to Customer), filter the payload by changed-field.

When company updated in Copper, create page in Notion.

Fires on any change to a company record — field edits, custom-field updates, owner reassignments. For specific transitions (e.g., status moved to Customer), filter the payload by changed-field.

When company updated in Copper, delete block in Notion.

Fires on any change to a company record — field edits, custom-field updates, owner reassignments. For specific transitions (e.g., status moved to Customer), filter the payload by changed-field.

When lead deleted in Copper, append content in Notion.

Fires when a lead is hard-deleted from Copper. Useful for compliance workflows ("ensure the lead was also removed from email tools") and for audit-trail workflows that log all CRM deletions.

How it works

Connect Copper and Notion in five steps.

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

1
Connect
Authorize Copper and Notion
Open Tiny Command, authorize Copper and Notion once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Copper trigger
Drop the Copper → Company Created trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/copper.trigger-company-created
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 Copper payload into the Notion inputs.
notion.append-blocks
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Copper + Notion.

How long does it take to connect Copper and Notion on Tiny Command?

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

Is the Copper ↔ Notion integration real-time?

Yes. Both Copper 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 Copper 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 Copper events can trigger a Notion workflow?

Any of the 10 Copper triggers, including "Company Created". Each fires in real time when the matching event happens in Copper.

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

No. There's a free tier that covers most Copper+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 → Copper instead?

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

Other apps that pair well with Copper.

Copper + Gmail

Copper + Slack

Communication

Copper + Google Sheets

Spreadsheets & Databases

Spreadsheets & Databases

Wire Copper to Notion in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo

Connect Copper to Notion in two minutes.

Pick the way that fits your stack.

When something happens in Copper, do it in Notion.

Or fire it the other way around.

Common Copper → Notion workflows.

Connect Copper and Notion in five steps.

Questions about Copper + Notion.

Other apps that pair well with Copper.

Wire Copper to Notion in 2 minutes.

Be the first to know what's next.