Set up Zapier, step by step

Connect Loopion to Slack, Monday.com, Asana, HubSpot and thousands of other apps in about five minutes. One connection by the workspace owner covers the whole team.

1

Open Settings → Integrations and create an API key

in Loopion

Sign in to Loopion as the workspace owner and go to Settings → Integrations. (Integrations are available on Business plans and above, and only owners see this page.)

Give the key a name you'll recognise — "Zapier" is fine — and click Create API key.

loopion.ai/settings/integrations

API keys

Use an API key to connect the Loopion app on Zapier — triggers for new actions, completed actions and ready summaries, with deep links back to Loopion.

Key name (e.g. Zapier)
Create API key
2

Copy the key — it's shown exactly once

in Loopion

The full key appears once, in the amber box. Copy it somewhere safe before leaving the page — afterwards only the first few characters are visible.

If you ever lose it, just revoke it and create a new one; revocation is instant.

loopion.ai/settings/integrations

Copy this key now — it won't be shown again:

lp_live_4f8a12c96be07d31e5a2b8f04c6d9e17a3b5c8d0f2e4a6b8
Zapier lp_live_4f8a…

Never used

Revoke
3

Add the Loopion app and paste your key

in Zapier

In Zapier, create a new Zap and search for Loopion as the trigger app. The first time, Zapier asks you to connect your account: paste the API key from step 2.

The connection is named after your workspace, and it covers your whole team — one key connects everyone's actions and meetings in the workspace, so nobody else needs to set anything up.

zapier.com — Connect Loopion

Allow Zapier to access your Loopion Account?

API Key

••••••••••••••••••••••••••••

Create an API key at Loopion → Settings → Integrations (workspace owners only). Keys look like lp_live_… and are shown once at creation.

Yes, Continue to Loopion
4

Choose your trigger

in Zapier

Pick the event that should start the Zap. New Action is the usual starting point — it fires whenever Loopion captures an action from any meeting in your workspace (or one is created manually).

Test the trigger: Zapier pulls in a sample so you can see exactly which fields are available — action title, owner name and email, due date, meeting title, and a link back to Loopion.

zapier.com — Zap editor · Trigger
Loopion· Trigger event

New Action

Triggers when Loopion captures a new action from a meeting.

Action Completed

Triggers when an action is completed in Loopion.

Action Reminder

Triggers when Loopion sends a follow-up reminder for an open action.

Meeting Summary Ready

Triggers when a meeting summary is ready in Loopion.

5

Send it wherever your team works

in Zapier

Add an action step for your destination — Slack, Monday.com, Asana, Jira, HubSpot, Google Sheets, or any of Zapier's thousands of apps.

Map the Loopion fields into the destination's boxes. For a Slack channel message, that's typically the action title, the owner, the due date, and the Loopion link.

Want personal delivery instead of a shared channel? Use Slack's Send Direct Message action and map Owner Email as the recipient — each person's actions reach them directly, still from this one Zap.

zapier.com — Zap editor · Slack action
#Slack · Send Channel Message

Channel

#team-actions

Message Text

New action: {{Action Title}} — owner {{Owner Name}}, due {{Due Date}}

Link

{{Link to Action in Loopion}}

Fields in {{curly braces}} are mapped from the Loopion trigger — pick them from the dropdown Zapier shows for each box.

6

Optional: sync completions back to Loopion

in Zapier

Loopion also provides a Complete Action step. Build a second Zap that fires when work is finished in your other tool (a Monday status change, a Jira transition, a Slack reaction) and map the stored Action ID into it.

Completion is recorded once and reflected everywhere — the action closes in Loopion, drops out of reminders, and shows as done in recaps and carry-forward.

zapier.com — Zap editor · Loopion action
Loopion · Complete Action

Action ID

{{Action ID}} — mapped from the Loopion trigger, or from where you stored it
When this runs, the action is marked Done in Loopion — including across its carry-forward history — so recaps and reminders stay accurate.
7

Turn the Zap on and test it end-to-end

in Zapier

Publish the Zap. From then on it runs automatically for every matching event in your workspace.

To see it work immediately: create a test action in Loopion (New Action Item on any meeting page) and watch it arrive in your destination within moments.

If something doesn't work

  • Connection fails in Zapier → the key was mistyped or revoked, or your workspace isn't on a Business plan or above. Create a fresh key and try again.
  • The trigger never fires → check the Zap is published (not draft), and that the event really happened — e.g. Action Reminder only fires when Loopion sends a reminder email for an open, owned action.
  • Slack DMs go to the wrong person → the owner's Loopion email must match their Slack email.
  • You revoked a key → every Zap using it stops immediately. Create a new key and reconnect the Loopion account in Zapier.
Privacy note: Zapier payloads carry action details and links back to Loopion — never transcripts, summaries or meeting content. Your meeting record stays in your workspace.