Resources · Zapier integration

Makeswift Zapier integrationAutomate Makeswift with Zapier.

The Makeswift Zapier integration gives you 1 trigger, 0 actions and 0 searches. Each new record added to a Makeswift table reaches Zapier the moment it lands, ready to be sent on to another tool. Zapier cannot write anything back into Makeswift.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Makeswift Zapier integration does for you

The Makeswift Zapier integration links your Makeswift account to Zapier so that a new record in one of your tables starts an automation in another app. It goes one way: Makeswift reports, your other tools act. The trigger is instant, and Makeswift is not a premium app, so the free plan is enough to start.

A heads-up for your team. New Record fires as soon as a record is added to the table you picked, so the people who need to know get a message in the chat they already watch, without checking Makeswift.

A copy kept elsewhere. The same trigger can feed a sheet or a database you report from, so each new record exists in two places without anyone exporting it.

A follow-up that starts itself. Whatever should happen after a record arrives, such as an email to a colleague, can hang off this one event.

What Zapier does not do here: Makeswift has no action and no search on Zapier. A Zap (an automation) cannot create or change a record in Makeswift, and it cannot look one up. It also only hears about new records, not edits or deletions. If your flow has to end inside Makeswift, Zapier alone will not cover it.

Weighing platforms? The n8n vs Zapier and Make vs Zapier comparisons set out the criteria.

Vocabulary

Zapier words, in one minute

Seven terms come back on this page. Each one, once, in plain words.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it, here a new Makeswift record.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app the moment it happens. New Record is instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
Cost

What it really costs

A new record reaching Zapier is free. Only what the Zap does next is billed.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Trigger speedInstant, whatever the plan

The trigger never costs a task. Each action that succeeds counts as one task; one that fails does not. The free plan gives 100 tasks a month and two-step Zaps, so New Record plus one message fits. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The grid below is Zapier's interval for polling triggers; it does not apply to New Record, which is instant on every plan.

Connect

Connect Makeswift to Zapier

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. You need a Makeswift account first; Zapier links an existing one, it does not create it.

  2. 02

    Pick Makeswift

    Type Makeswift in the search box of the dialog, select it and click Add connection. A new tab opens on the Makeswift side so you can sign in with your usual login.

  3. 03

    Sign in and grant access

    Log in to Makeswift in that tab and allow Zapier to reach the account. Use a login that can see the workspace and the table you plan to watch, even if someone else owns them.

First Zap

Your first Zap: post new Makeswift records to your team chat

GoalWhen a record is added to a chosen Makeswift table, post a message in your team chat, only for records that meet your condition.

  1. 01

    Create the Zap

    Start a new Zap, pick Makeswift as the app that starts it and New Record as the event, then choose your connection. A lightning bolt shows the trigger is instant.

  2. 02

    Choose where to listen

    Pick the Workspace, then the Table to watch. Both are required, so the trigger cannot be set up without them. Pick the table whose new records matter to you.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent records, so you map the next steps on a real record rather than a guess.

  4. 04

    Add the filter

    Add a filter from the plus icon and fill its three boxes: the field, the rule, the value. Use a text rule for text and a number rule for numbers.

  5. 05

    Add the message and publish

    Add your chat tool as the action, put the record's details into the message, test it once, then click Publish. With the filter, this needs a paid plan.

Triggers

Makeswift triggers

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

1

New Record

Instant trigger

In Zapier“Triggers when a new record is added.”

Starts your Zap whenever a record is added to the Makeswift table you picked, and hands its content to the next step so other tools can use it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
new records in a table should reach your team, a sheet or an inbox without anyone opening Makeswift to look.
Watch out
Workspace and Table are both required, and the connected login needs access to that table.
When it breaks

When it breaks

Zapier links no help article and no app-specific limit to Makeswift. What can go wrong comes from how Zapier itself works.

Three cases to know before you publish. If a run fails anyway, our Zapier troubleshooting guide is the place to start.

  • Existing records are never picked up

    A Zap only reacts to what happens after you switch it on. Records already in the table stay where they are; moving that backlog is a separate job.

  • A sudden batch can be held back

    If the trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.

  • A filter needs a paid plan

    The free plan builds two-step Zaps only. A filter between New Record and your action makes the Zap multi-step, and it stops fitting the free plan.
Need help

Need help automating Makeswift with Zapier?

A person reads every message.

FAQ

Makeswift Zapier integration: common questions

01Is the Makeswift Zapier integration free?
Yes. Makeswift is not a premium app on Zapier, so it works on the free plan. That plan gives 100 tasks a month and Zaps of two steps, one trigger and one action, which is enough to send each new record to one other tool. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. You also need your own Makeswift account, since Zapier only links an existing one.
02How many tasks does a Makeswift Zap use?
The trigger uses none: a new record reaching Zapier is free. Each action that completes successfully counts as one task, per record. A Zap that posts one message uses one task per new record; a Zap with three actions uses three. An action that fails is not counted against your plan. On the free plan you have 100 tasks a month, so you can estimate how many records that covers.
03Does Makeswift reach Zapier in real time?
Yes. New Record is an instant trigger: Makeswift tells Zapier as soon as a record is added, and the Zap starts right away. The checking interval of your plan, which applies to polling triggers, does not apply here, so it is as fast on the free plan as on a paid one. In the editor, a Zap built on this trigger shows a lightning bolt. That cannot be changed from the Zapier side.
04What does it take to connect Makeswift to Zapier?
A Makeswift account, with a login that can see the workspace and the table you want to watch, including ones you do not own. In Zapier, open the Apps page, click + Add connection, search for Makeswift, click Add connection, sign in on the tab that opens and grant access. The connection is then reused by every Makeswift Zap, so you set it up once and simply pick it from a list in later Zaps.
05What does New Record need before it can run?
A Workspace and a Table, both required. Zapier acts with the login you connected, so that login needs access to the workspace and the table, even when someone else owns them. Check those rights in Makeswift before you build, or connect a login that already has them. Then test the trigger: Zapier brings back the three most recent records, and you map the next step on a real one instead of a guess.
06What if the Makeswift operation you need is missing?
Then Zapier does not offer it today. The Makeswift app on Zapier has one trigger, New Record, and nothing else: no action to create or edit a record, no search to find one, no trigger for changes or deletions. A flow that must write into Makeswift cannot be built with this integration alone. Zapier can still carry new records out to other tools, so check whether the step can happen on the receiving side.
07Zapier, Make or n8n for Makeswift?
Decide on criteria rather than on a ranking. First, check which platform actually offers a ready-made Makeswift connection with the events you need; on Zapier that is one instant trigger. Second, compare billing: Zapier counts tasks, meaning successful actions, and the trigger is free. Third, think about direction: here data only leaves Makeswift, so the tools that receive it matter as much as the platform in between. Weigh those three points against the tools your team already uses.
Same platform

Other docs you might need on this stack.

Browse all integrations