Resources · Zapier integration

MagicBlocks Zapier integrationAutomate MagicBlocks with Zapier.

The MagicBlocks Zapier integration gives you 5 triggers, 9 actions and 0 searches. All five triggers are instant, so a finished conversation, a completed goal or an updated contact reaches your other tools straight away, whatever your plan.

See the 14 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MagicBlocks Zapier integration does for you

MagicBlocks runs AI sales agents that talk with your leads. Connecting it to Zapier means what those agents learn leaves MagicBlocks on its own: a conversation that ends, a goal reached or a contact that changes sets off a chain of steps in your other tools, with nobody copying anything by hand.

Three results come up again and again. A written recap of each qualified lead: Goal Completed starts the Zap, Summarize Session condenses the conversation, and your sales tool gets the gist instead of a raw transcript. A contact record that stays in sync: Contact Created or Updated pushes every change outward, while Create Contact and Update Contact bring people in from elsewhere. An agent that reacts to outside events: Start Experience and Run Experience let another app open or continue a conversation with one of your agents.

What it does not do on Zapier: MagicBlocks has no search step, so there is no built-in way to look a record up before writing it. The closest thing is Find Contact, which is an action, so it counts as a task like any other. Several actions also expect a Contact Id and a Session Id; if no earlier step carries them, those actions cannot run.

If you are still weighing the tool, see our Zapier review and our Make vs Zapier comparison. We have no MagicBlocks page for n8n or Make at this point.

Vocabulary

Zapier vocabulary, in plain words

Seven words come back on every Zapier page. Here they are once, so the rest reads easily.

Zap
The automation you build: one trigger, then one or more actions that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event to happen.
Action
What the Zap does after it starts: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills you for: one action your Zap completes successfully. Your plan is a count of these.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by the app the moment it happens.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
Cost

What a MagicBlocks Zap really costs

MagicBlocks is not a premium app, so it works on the free plan. You pay in tasks, and only actions use them.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan stepsOne trigger and one action
  • MagicBlocks triggers5, all instant
  • Failed actionNot counted against your plan

A trigger never costs a task, so the five MagicBlocks triggers are free to listen to. Each action that succeeds counts once, and one that fails does not count. Summarizing a session and then sending the summary to another tool is two actions, so two tasks per conversation, and that second action makes it a multi-step Zap, which needs a paid plan. The free plan stops at one trigger and one action. The interval grid below is Zapier's standard one; it does not apply to MagicBlocks, whose five triggers are all instant.

Connect

Connect your MagicBlocks account in three steps

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. You need a MagicBlocks account first, since Zapier only links an account that already exists.

  2. 02

    Pick MagicBlocks

    Type MagicBlocks in the search box of the dialog that appears, select it in the results, then click Add connection. A new browser tab opens on the MagicBlocks side.

  3. 03

    Sign in and allow access

    Log in to MagicBlocks in that tab and grant Zapier access to your workspace. The connection is saved once, and every Zap step that uses MagicBlocks reuses it from then on.

First Zap

Your first Zap: send a recap of every qualified lead

GoalWhen a MagicBlocks agent completes its goal with a lead, Zapier summarizes the conversation and adds the summary to your sales tool.

  1. 01

    Start from Goal Completed

    Build a new Zap with MagicBlocks as the app and Goal Completed as the event. It is instant, so the Zap starts as soon as the agent reaches its goal.

  2. 02

    Set the Type to live

    The trigger requires a Type. Choose live so that only real conversations count, then test: Zapier brings back the three most recent matching sessions of your account.

  3. 03

    Add Summarize Session

    Add MagicBlocks as the action and choose Summarize Session. Map the Contact Id and Session Id that the trigger brought back; both fields are required.

  4. 04

    Send the recap on

    Add your sales tool as a third step and map the summary into a note. This extra action makes the Zap multi-step, so it needs a paid plan to run.

  5. 05

    Test, then publish

    Test each step once and read the summary MagicBlocks returns. When it reads well in your sales tool, publish the Zap to switch it on.

Triggers

The 5 MagicBlocks triggers

5 events start a Zap when something happens in MagicBlocks, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Contact Created or Updated

Instant trigger

In Zapier“Triggers when a contact is created or updated.”

Starts the Zap whenever a contact appears in your MagicBlocks workspace or one of its details changes, and hands that contact to the next steps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your agents collect names, emails and phone numbers during conversations and you want that record mirrored in your sales tool without retyping it.
Watch out
a Zap that writes back to the same contact with Update Contact may set itself off again; test that case before publishing, or tasks can drain in a loop.
2

Form Completed

Instant trigger

In Zapier“Triggers when a form is completed.”

Fires when a lead finishes a form inside a MagicBlocks session, so whatever they filled in can travel to another app.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the form is where your agent gathers qualifying answers, and you want those answers stored or acted on as soon as the lead submits them.
Watch out
the required Type field decides whether live sessions, test sessions or both count, so set it to live before you publish.
3

Goal Completed

Instant trigger

In Zapier“Triggers when a goal is completed.”

Reacts when a conversation reaches the goal you set for the agent, which makes it the cleanest signal that a lead is worth following up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you only want to hear about conversations that succeeded, not every chat that started, for instance to alert a salesperson or log a qualified lead.
Watch out
it carries the same required Type choice as the session triggers, and test runs will fire it if you leave Type on all.
4

Session End

Instant trigger

In Zapier“Triggers when a session ends.”

Kicks off the Zap at the close of each session, whether or not the goal was reached, so you can deal with the full conversation once it is over.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want every finished conversation archived or summarized, including the ones that did not convert, to see where leads drop off.
Watch out
it fires on every session, so a busy agent can use your tasks fast if each run triggers several actions; a filter can narrow it, on a paid plan.
5

Session Started

Instant trigger

In Zapier“Triggers when a session starts.”

Goes off the moment a new session opens with one of your agents, before anything has been said or qualified.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a heads-up that someone is talking to your agent right now, for example to count conversations or warn a teammate who might step in.
Watch out
it fires on every opening, even for a chat that goes nowhere, and Type must still be set to live, test or all.
Actions

The 9 MagicBlocks actions

MagicBlocks gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Contact

Action

In Zapier“Creates a contact in your workspace”

Adds a new contact to your MagicBlocks workspace from data another app sends.

When to use it
leads arrive from a form or an event outside MagicBlocks and you want your agents to know them before the first conversation.
Watch out
the Type field is required, so decide up front which kind of contact you are creating.
2

Find Contact

Action

In Zapier“Finds a contact by id or email or phone from your workspace”

Looks up an existing contact by id, email or phone and returns it to the following steps.

When to use it
another tool only knows a lead by email or phone number and you need the matching MagicBlocks record before updating it.
Watch out
this is an action, not a Zapier search step, so each lookup that succeeds costs a task.
3

Get Session

Action

In Zapier“Get Session by id from your workspace”

Fetches the details of one session so later steps can use them.

When to use it
your trigger came from another app but carries the session reference, and you need the session itself before acting.
Watch out
Contact Id and Session Id are both required; without them the step has nothing to fetch.
4

Get Session Messages

Action

In Zapier“Get a sessions messages.”

Pulls the messages exchanged during a session, the actual back and forth between the lead and your agent.

When to use it
you want the full conversation stored next to the lead, not just a summary.
Watch out
like Get Session, it needs both the Contact Id and the Session Id from an earlier step.
5

Run Experience

Action

In Zapier“Run or continue an Experience on your workspace.”

Runs or continues an Experience with one of your agents, sending it a message through a given channel source.

When to use it
a reply or an event in another tool should move an ongoing conversation forward without anyone opening MagicBlocks.
Watch out
it has four required fields (Agent Id, Source, Message and Mode), so check each one is mapped.
6

Start Experience

Action

In Zapier“Start a new experience on your workspace”

Opens a brand-new Experience with one of your agents on the channel you pick.

When to use it
an event in another app should prompt your agent to open the conversation instead of waiting for the lead.
Watch out
Agent Id, Mode and Channel are all required, so keep your agent's id at hand when you set it up.
7

Summarize Session

Action

In Zapier“Summarize a session from your workspace.”

Turns a whole session into a short summary you can pass to a person or another app.

When to use it
your sales team wants the gist of each qualified conversation, not pages of chat.
Watch out
map the Contact Id and Session Id from the trigger; the step fails if either one is empty.
8

Update Contact

Action

In Zapier“Updates a contact in your workspace.”

Changes the details of a contact already in your workspace.

When to use it
another tool learns something new about a lead, a new phone number for instance, and MagicBlocks should hold it too.
Watch out
in a Zap started by Contact Created or Updated, it may set the trigger off again and loop; check the run history after your first test.
9

Update Session

Action

In Zapier“Update a session in your workspace”

Edits a session that already exists in your workspace.

When to use it
a decision taken in another tool after the conversation needs to be reflected on the session itself.
Watch out
it requires the Contact Id and the Session Id, so it belongs after a session trigger or Get Session.
When it breaks

When a MagicBlocks Zap breaks

Zapier attaches no help article to MagicBlocks, so the known failure points are the ones every Zap shares, plus one setting of its own.

None of them shows up as a clear message until you look at the runs. If a Zap still puzzles you, see our Zapier troubleshooting page.

  • Past conversations are ignored

    A Zap only reacts to what happens after you switch it on. Sessions and goals that ended earlier are not picked up; moving that history is a separate job.

  • The contact Zap may keep firing

    A Zap started by Contact Created or Updated that writes back to the same contact with Update Contact can set itself off again and again, and burn through your tasks.

  • Test sessions reach your tools

    Every trigger requires a Type of live, test or all. On test or all, the conversations you run to try your agent start the Zap like real ones.

  • A bulk import gets held back

    When a trigger suddenly sends a huge batch, after an import of contacts for example, Zapier's flood protection can hold those runs back.
Need help

Need help automating MagicBlocks with Zapier?

A person reads every message.

FAQ

MagicBlocks Zapier integration: your questions

01Is the MagicBlocks Zapier integration free?
On Zapier's side, yes. MagicBlocks is not a premium app, so the free plan covers it: 100 tasks a month and as many Zaps as you like, each capped at one trigger and one action. Goal Completed followed by Summarize Session fits inside that. Sending the summary on to your sales tool adds a second action, and that moves the Zap to a paid plan. What MagicBlocks charges for its own account is outside the scope of this page.
02How many tasks does a MagicBlocks Zap use?
One per action that succeeds, and nothing for the trigger. A Zap that fires on Session End, fetches the messages and then summarizes them uses two tasks per conversation. Find Contact counts too, because on Zapier it is an action rather than a search step. Actions that fail are not counted. With Session End firing on every conversation, a busy agent multiplies quickly, so count your sessions before choosing a plan.
03Do MagicBlocks Zaps run in real time?
Yes, on every plan, free included. MagicBlocks reports each event to Zapier itself: a contact that changes, a form that gets completed, a goal reached, a session opening or closing. Nothing waits for a timer, so the interval grid on this page never applies to these five triggers. Look for the lightning bolt on the Zap in the editor. It is not a setting you can turn on; the app decides. The real thing to watch is volume, since a busy agent starts one run per session.
04What does connecting MagicBlocks to Zapier require?
Two things: a MagicBlocks account, and rights on any workspace that is not yours. Then head to the Apps page in Zapier, click + Add connection, search for MagicBlocks, log in on the tab that opens and grant access. That is a one-time job; every MagicBlocks step in every Zap reuses the same connection afterwards. If a colleague set up the workspace your Zap will touch, make sure your account has read or write access there before the first test.
05Why do test conversations show up in the sales tool?
Because the trigger's Type was left on test or all. Every MagicBlocks trigger requires that choice: live, test or all. Test sessions are the ones you run to try your agent, and with all selected they start the Zap exactly like a real lead would. Switch the Type to live on each trigger, test it again, and only genuine conversations will reach your other tools from then on. Do the same on every trigger you use, since each one has its own Type setting.
06What if the MagicBlocks operation that's needed is not listed?
Then Zapier does not offer it for MagicBlocks. The editor shows five triggers and nine actions, and no search step. Some needs can still be met by combining what is there: Find Contact followed by Update Contact covers a lookup then a change, and Get Session followed by Get Session Messages covers reading a conversation. Each extra action makes the Zap multi-step, which requires a paid plan. Check the action list in the editor before building around a missing piece.
07Zapier, Make or n8n for MagicBlocks?
Decide on criteria rather than a ranking. Speed: on Zapier the five MagicBlocks triggers are instant, so plan level does not slow them down. Cost: Zapier counts one task per successful action, and Session End fires on every conversation, so volume matters. Coverage: Zapier has no search step for this app, so check what the other platforms offer for MagicBlocks before you move a workflow across. A short test on each platform tells you more than any table.
Same platform

Other docs you might need on this stack.

Browse all integrations