Resources · Make integration

Swipe One Make integrationAutomate Swipe One with Make.

Want every new lead to land in Swipe One without typing it in? The Swipe One Make integration gives you 2 action modules, one for contacts and one for events. This page shows how to link your account and build a first scenario that feeds Swipe One from another app.

Try the Swipe One integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Swipe One Make integration do for you?

The Swipe One Make integration lets a scenario, the automation you build in Make, write into your Swipe One CRM for you. It has 2 modules, the bricks of a scenario: one creates or refreshes a contact, the other records an event. Both are actions, so the scenario starts from another app or from a schedule.

A contact list that fills itself. A web form or a booking tool sends each new entry to Make, and Create or Update Contact writes it into Swipe One. No copy and paste. Going by its name, the module updates a known person instead of only creating new ones.

A history of what each customer did. After the contact step, Record Event logs what happened in Swipe One, so your sales team can find what happened when it follows up. A shop could use it for an order, a coach for a booked call.

One CRM fed by several tools. The same pair of modules can sit at the end of different scenarios, one per source app. Browse the 123FormBuilder Make integration for a form-based starting point.

What Make does not offer here: Swipe One has no trigger module and no Make an API Call module, so Make cannot react to a change made inside Swipe One. If you are weighing tools, the n8n vs Make comparison lays out both, and the Make training covers the editor basics.

Connect

How do you connect Swipe One to Make?

  1. 01

    Copy your API key

    In Swipe One, open Settings in the left sidebar, then the Workspace tab. The API key is shown on screen: copy it. You need an active Swipe One account for this.

  2. 02

    Create the connection

    In your Make scenario, add a Swipe One module and click Create a connection. A connection is your Swipe One account linked to Make once, then reused by both modules. You can name it in the Connection name field.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, and confirm. The module then opens its settings, ready to fill.

First scenario

Your first scenario with Swipe One

GoalWhen a new entry arrives from another app, Make creates or updates the contact in Swipe One and records an event on it.

  1. 01

    Start from the source app

    Create a new scenario from the Scenarios page and click the +. Pick the module of the app that holds your leads, such as a form tool, and connect it.

  2. 02

    Add Create or Update Contact

    Click the + on the right of the first module, search Swipe One and choose Create or Update Contact. Select your connection, then map the person's details from the first module.

  3. 03

    Add Record Event

    Add one more module after it: Record Event. Fill its fields with what should appear in the contact's history, using data from the earlier modules.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one person. Check Swipe One to see the contact and the event.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Keep that or adjust it within your plan, then switch the scenario on.

Modules

What the Swipe One modules do

Swipe One gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Swipe One1

Create or Update Contact

ActionIn the docs only

This module keeps one clean record per person in Swipe One: as its name says, it creates the contact when needed and updates it otherwise. You get a CRM that stays current without manual entry.

When to use it
right after a form, a booking or a purchase in another app, as the step that brings the person into Swipe One.
Watch out
Make's documentation gives no field list, so open the module once the connection exists and read what it asks for.
Swipe One2

Record Event

ActionIn the docs only

Going by its name, Record Event logs in Swipe One something a person did, which gives your team context before the next email or call. Place it after the contact step in the same scenario.

When to use it
when the fact that matters is an action, such as a signup, rather than a change to the contact itself.
Watch out
each run costs one operation, a single module execution Make counts on your plan, so avoid firing it on data that changes nothing.
Need help

Need help automating Swipe One with Make?

A person reads every message.

FAQ

Swipe One and Make: common questions

01Is the Swipe One Make integration free?
Yes, on the Make side. Swipe One is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month. You still need your own Swipe One account, with its own subscription.
02What do you need to connect Swipe One to Make?
An active Swipe One account and its API key. You find the key in Swipe One under Settings, in the left sidebar, on the Workspace tab. In Make, add a Swipe One module, click Create a connection, give it a name if you like, and paste the key. That connection is then reused by both Swipe One modules, so you only do this once per account. If the key is refused, copy it again from the Workspace tab.
03Can Swipe One start a Make scenario in real time?
No. Swipe One has no trigger module in Make, so it cannot start a scenario on its own. The scenario starts elsewhere: either from another app's trigger, for example a form tool that calls Make through a webhook as soon as someone submits, or from Make's own schedule on the first module, every 15 minutes by default. Swipe One then acts as the destination, where Create or Update Contact and Record Event write the data. On the Free plan, scheduled runs are at least 15 minutes apart.
04What if the Swipe One module you need is missing in Make?
It depends on what you need. The integration covers two actions, contacts and events, and Swipe One has no Make an API Call module, so you cannot reach other parts of Swipe One through Make. The practical options are to reshape the scenario around those two actions, to let another app handle the step Swipe One cannot, or to ask the team for help designing the flow. The troubleshooting guide also helps you read an error message.
05Make or n8n for Swipe One?
It depends on the tool you already run. On Make, Swipe One offers two actions and no trigger, so the choice mostly comes down to where the rest of your scenarios live. The same app often has an n8n node as well, so check its list of operations against what you need before you pick. Keeping your automations in one tool means one place to monitor. The comparison between n8n and Make, linked above, sets out the criteria without declaring a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations