Resources · Zapier integration

Magnetite Zapier integrationAutomate Magnetite with Zapier.

The Magnetite Zapier integration offers 1 trigger, 1 action and 1 search. A Magnetite project event can start a Zap at once, an email address is enough to order a personalized lead magnet, and a status search tells you where the generation stands.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Magnetite Zapier integration is for

Magnetite builds personalized lead magnets with a research agent, to turn cold emails into meetings. On Zapier it plugs into Zaps, the automations you set up there: one event starts them, then steps run for you. Magnetite can start a Zap, receive an order for a lead magnet and report on its progress.

Three results come out of it. A lead magnet ordered from a single email address: Create Lead Magnet asks your Magnetite research agent to build one for that contact, wherever the address came from. A clear view of each job: Find Lead Magnet Status takes the Job ID returned by the creation step and tells the rest of the Zap how far the generation has got. Your other tools kept in the loop: New Event sends a chosen type of project event out of Magnetite, to a CRM, a sheet or a chat.

Good news for a free plan: New Event is an instant trigger, so the checking interval of your plan never applies to it.

What Zapier does not do for Magnetite: no action edits or deletes a lead magnet, the only search works by Job ID, so you cannot look one up by email, and a New Event Zap listens to one event type at a time. To weigh Zapier against another platform, our n8n vs Zapier comparison sets out the criteria.

Vocabulary

Zapier vocabulary in one minute

Seven words cover nearly everything in the Zapier editor. Each one explained once.

Trigger
The event that starts a Zap. With Magnetite, it is a project event of the type you select.
Action
What the Zap does once started. On Magnetite, the one action orders a personalized lead magnet.
Task
The unit Zapier bills: one action that went through. Your plan allowance counts these and nothing else.
Instant trigger
A trigger the app reports itself, the moment the event happens. New Event on Magnetite works this way.
Polling trigger
A trigger Zapier checks on a timer, keeping only what is new. Magnetite has none on Zapier.
Search step
A step that looks up something that already exists, so later steps can use it. Here, the status of a job.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A search, a filter or a second action makes one, and needs a paid plan.
Cost

What a Magnetite Zap costs

Magnetite is not a premium app, so the free plan covers it. You pay in tasks: successful actions only.

  • Premium appNo, free plan works
  • Trigger typeInstant
  • Free plan100 tasks a month, two-step Zaps
  • Search stepMakes the Zap multi-step, paid plan

A Magnetite event costs nothing on its own, whatever the volume. Each action that completes counts one task, in Magnetite or in the next app; a failed one counts nothing. The free plan gives 100 tasks a month and two-step Zaps, so adding Find Lead Magnet Status, a filter or a second action takes you to a paid plan. The interval grid below concerns polling triggers and does not apply to New Event, which is instant.

Connect

Connect Magnetite to Zapier in 3 steps

  1. 01

    Open the Apps page

    In Zapier, go to the Apps page of your account and click + Add connection. You need a Magnetite account, plus access to the project you want the Zap to work with if someone else owns it.

  2. 02

    Pick Magnetite

    Search for Magnetite in the dialog, select it from the results and click Add connection. A new browser tab then opens for the sign-in on the Magnetite side.

  3. 03

    Sign in and grant access

    Log in to Magnetite in that tab and allow Zapier to use the account. The connection is saved, and every Zap that uses Magnetite reuses it from then on.

First Zap

Your first Zap: selected Magnetite events logged in your CRM

GoalMagnetite project events that meet your condition become notes in your CRM.

  1. 01

    Create the Zap

    Start a new Zap, pick Magnetite as the app that starts it and New Event as the trigger, then choose the Event Type that should fire it.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent events of that type from your account, so you map fields on a real one.

  3. 03

    Add the filter

    Add a Filter step and fill its three boxes: the field to look at, the rule, the value to compare with. The filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the CRM note

    Add the action of your CRM that creates a note, pick where the note should go, then drop the event details that came back in the test from Magnetite into the note body.

  5. 05

    Test and publish

    Test the note, check it in the CRM, then publish. Since New Event is instant, each matching event arrives straight away, whatever your plan.

Triggers

The Magnetite trigger

1 event starts a Zap when something happens in Magnetite, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

New Event

Instant trigger

In Zapier“Triggers when a specific event occurs in your Magnetite project.”

Starts a Zap when a given kind of event happens in your Magnetite project. One trigger covers several situations: you choose which one matters in the Event Type setting, and the Zap stays quiet for everything else that happens in the project.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a step in your outreach should move another tool forward, such as a CRM record or a team alert.
Watch out
Event Type is required and holds one value, so following two kinds of events means building two Zaps.
Actions

The Magnetite action

Magnetite gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Lead Magnet

Action

In Zapier“Create a personalized lead magnet using your Magnetite research agent”

Asks your Magnetite research agent to produce a personalized lead magnet for one contact. The only required field is the contact's Email Address.

When to use it
each time a new prospect lands in a list or a form, so the material is ready before the first email.
Watch out
keep the Job ID it returns; Find Lead Magnet Status needs it.
Searches

The Magnetite search

1 search step looks for data that already exists in Magnetite, so a later step can use it.

A search step looks up something that already exists and hands what it found to the next steps. Searches sit at the bottom of the action event list, under the SEARCH heading. Three settings decide what happens when the result is not the expected one.

1

Find Lead Magnet Status

Search

In Zapier“Search for the status and progress of a lead magnet generation job”

Checks how far a lead magnet generation has progressed and hands its status to the steps that follow. It needs the Job ID from the creation step earlier in the Zap. The field help calls that step Generate Lead Magnet; in the list it is Create Lead Magnet, the only action.

When to use it
just after Create Lead Magnet, to decide what the Zap does next.
Watch out
if nothing is found, the Zap stops there unless you change the setting.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that depend on it. Switched on, the Zap carries on without a result.
  2. Create X if it doesn't exist yet?
    This box turns a search into find or create. Magnetite offers no such variant on Zapier, so Find Lead Magnet Status only ever looks.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When a Magnetite Zap breaks

Zapier ties no help article to Magnetite, so the weak points are Zapier's general limits.

They rarely announce themselves. A note is missing, or the task count jumps. To chase the cause in order, see our Zapier troubleshooting guide.

  • Past events never arrive

    A Zap only reacts to what happens after it is switched on. Events from before stay in Magnetite; moving that history is a separate job.
  • Writing back into Magnetite

    A Zap that writes where its own trigger watches restarts itself and burns tasks. As a general precaution, think twice before sending a New Event Zap into Create Lead Magnet.
  • A burst held back

    When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of running them all.
  • A status search that stops the Zap

    With default settings, Find Lead Magnet Status that finds nothing halts the Zap there. Check the Job ID mapping first.
Need help

Need help automating Magnetite with Zapier?

A person reads every message.

FAQ

Magnetite Zapier integration: frequently asked questions

01Is the Magnetite Zapier integration free?
Yes, for two-step Zaps. Magnetite is not a premium app, so the free plan covers it, with 100 tasks a month and Zaps of one trigger plus one action. New Event sending a note to your CRM fits that shape, and so does a form feeding Create Lead Magnet. The moment you add Find Lead Magnet Status, a filter or a second action, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Magnetite Zap use?
One per action that succeeds, and nothing for the trigger. A Magnetite event costs nothing by itself, and a failed action is not counted. Create Lead Magnet that goes through counts one task, and any action that follows in another app counts its own. So a Zap that orders a lead magnet and then posts to a chat spends two tasks per run. Count your steps before you plug a large list into it.
03Is the Magnetite Zapier integration real time?
Yes, on the trigger side. New Event is instant: Magnetite tells Zapier the moment the event happens, and the Zap starts right away whatever your plan. The polling intervals of the plans, from 15 minutes on Free to 1 on Team and Enterprise, do not apply to it. In the editor, a Zap built on an instant trigger shows a lightning bolt. The lead magnet itself is generated by Magnetite, and its progress is what the status search reports.
04What does it take to connect Magnetite to Zapier?
A Magnetite account you can sign in to, plus access to the project the Zap will use if you do not own it. In Zapier, open the Apps page, click + Add connection, choose Magnetite, click Add connection, then sign in to Magnetite in the tab that opens and grant access. On the trigger, you will also have to pick an Event Type, which is required, so know which project event should start the Zap.
05Where does Find Lead Magnet Status get its Job ID?
From the lead magnet creation step placed earlier in the same Zap. The Job ID is the only required field of Find Lead Magnet Status, and Zapier's own field help says to map it from the Job ID output of that step. That help text calls the step Generate Lead Magnet, while the action list shows Create Lead Magnet; the integration has only one action, so it is the step to use. Build the Zap with Create Lead Magnet first, test it so the Job ID appears, then map it into the search. That makes the Zap multi-step, so it needs a paid plan.
06What if the Magnetite operation the job requires is missing?
Then Zapier cannot do it with Magnetite today. The integration offers one trigger, New Event, one action, Create Lead Magnet, and one search, Find Lead Magnet Status. Nothing edits or deletes a lead magnet, and the search only works with a Job ID, so finding a lead magnet by email is not possible. If the job depends on one of those, check what other automation platforms expose for Magnetite first, before building anything.
07Zapier, Make or n8n for Magnetite?
Decide by criteria. Speed: New Event is instant on Zapier, so timing is not a reason to leave. Coverage: one trigger, one action and one search by Job ID; if the job needs more, compare with what other platforms expose. Flow size: creation plus status check already makes a multi-step Zap on a paid plan. Billing: every successful action is a task, so check how many steps each new contact will go through.