Resources · Make integration

SimpleCirc Make integrationAutomate SimpleCirc with Make.

Stop retyping subscribers into SimpleCirc by hand. The SimpleCirc Make integration gives you 10 modules: 1 scheduled trigger, 8 actions and 1 search. This guide is for publishers who run subscriptions, and it walks you from the API token to a first working scenario.

Try the SimpleCirc integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SimpleCirc Make integration automate?

The SimpleCirc Make integration links your SimpleCirc account to Make, a no-code tool where you build a scenario: the automation itself, made of modules chained one after the other. Each module is one brick, such as a trigger, an action or a search, and your SimpleCirc data flows between them without any code.

New readers land in SimpleCirc on their own. Someone signs up through a form or a shop you already use. Make passes that person to Create a Subscriber, then to Create a Subscription, and your circulation list is complete without a copy and paste.

Address changes stop getting lost. When a reader sends a new mailing address, Update an Address writes it on the right record, and Create an Address covers a reader who never had one.

Your other tools learn what happens in SimpleCirc. Watch Events checks SimpleCirc on the scenario's schedule and hands each new event to the rest of the scenario, for a sheet, a message or a CRM.

What Make does not give you here: the SimpleCirc documentation on Make lists the modules without describing their fields, and it warns that it is AI-generated and may contain mistakes. Test every module with a real record before you rely on it. For a broader look at the platform, read our Make review, and if you are weighing tools, the n8n vs Make comparison sets out the criteria. Plans and limits are covered on Make pricing.

Connect

How do you connect SimpleCirc to Make?

  1. 01

    Copy your SimpleCirc API token

    Make talks to SimpleCirc through an API token, so fetch it first. In SimpleCirc, open Account Settings, click the API tab and copy the token shown on screen. You need an active SimpleCirc account for this.

  2. 02

    Add a SimpleCirc module in Make

    In your Make scenario, add any SimpleCirc module and click Create a connection. A connection is your SimpleCirc account linked to Make once, then reused by every SimpleCirc module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the token and save

    Paste the API token you copied into the connection window and save it. From here on, every SimpleCirc module in your scenarios picks that same connection from a dropdown instead of asking again.

First scenario

Your first scenario with SimpleCirc

GoalWhen a new reader signs up in another app, Make creates the subscriber in SimpleCirc and opens a subscription for them.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where signups arrive, such as your form or shop tool, and its trigger.

  2. 02

    Add Create a Subscriber

    Click the + on the right of that first module, search for SimpleCirc and pick Create a Subscriber. Choose your connection, or click Create a connection if you have none yet.

  3. 03

    Map the reader's details

    Fill the subscriber fields by mapping data from the first module: each signup arrives as a bundle, one item passed from module to module. Make shows the values it received so you can drop them in place.

  4. 04

    Add Create a Subscription

    Add a third module with the +, pick Create a Subscription and map the subscriber that the previous module just created, so the new subscription lands on the right person.

  5. 05

    Test with Run once

    Click Run once, then send a test signup. Open the bubble above each module to read the bundles it received and check in SimpleCirc that the subscriber and subscription exist.

  6. 06

    Schedule and switch on

    Set the schedule on the first module with the clock. A new scenario checks every 15 minutes by default. Then switch the scenario on, and each new signup follows the same path.

Triggers

What starts a SimpleCirc scenario

1 module starts a scenario when something happens in SimpleCirc. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SimpleCirc as soon as it happens.

SimpleCirc1Watch Events

Watch Events

triggerIn the docs only

Watch Events gives your scenario a starting point inside SimpleCirc: each new event it finds becomes a bundle that the next modules can use. The Make documentation does not say which events SimpleCirc reports, so read the first results before building on them.

How it fires
scheduled, so Make checks the app on the scenario's schedule, every 15 minutes by default, with the clock badge on the module.
When to use it
you want another tool, such as a sheet or a team chat, to hear about activity in SimpleCirc.
Watch out
click Run once and look at what comes back before mapping anything, since the event contents are not documented.
Modules

What SimpleCirc can do in Make

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

SimpleCirc1

Create a Subscriber

ActionIn the docs only

Adds a new person to SimpleCirc straight from your scenario, so a signup captured elsewhere shows up as a subscriber without anyone typing it in.

When to use it
a reader fills in a form or buys through a shop that is not SimpleCirc.
Watch out
run List Subscribers first if the same reader might already exist, or you may end up with duplicates.
SimpleCirc2

Create a Subscription

ActionIn the docs only

Opens a subscription in SimpleCirc from data your scenario already holds, which turns a paid order or a signup into an active record you can serve.

When to use it
right after Create a Subscriber, or when an existing reader takes a new title.
Watch out
map the subscriber carefully, because a subscription tied to the wrong person is harder to spot than a missing one.
SimpleCirc3

Create an Address

ActionIn the docs only

Records a mailing address in SimpleCirc, which gets a new reader ready for delivery without a separate trip into the app.

When to use it
the subscriber exists but has no address yet, for example after a digital signup that turns into a print order.
Watch out
when the reader already has an address, Update an Address is the right choice, not a second record.
SimpleCirc4

Get a Subscriber

ActionIn the docs only

Brings back the record of one subscriber you already know, so later modules can reuse details that live in SimpleCirc instead of asking for them again.

When to use it
an event or another app gives you a single reader and you need the full record before acting.
Watch out
it works on one known subscriber; to find people when you are unsure who matches, List Subscribers is the better fit.
SimpleCirc5

List Subscribers

SearchIn the docs only

Searches your SimpleCirc readers and returns every match as its own bundle, which is how you check who is already there before creating anyone.

When to use it
before Create a Subscriber, to avoid a duplicate, or to feed a list into a sheet.
Watch out
a search can return zero, one or several bundles, and each bundle runs the following modules again, which costs operations.
SimpleCirc6

Make an API Call

ActionIn the docs only

Reaches any endpoint of the SimpleCirc API with the connection you already set up, which covers the jobs the nine other modules do not.

When to use it
you need something SimpleCirc offers through its API but no module lists.
Watch out
you write the request yourself, so keep the SimpleCirc API reference open and test with Run once before the scenario goes live.
SimpleCirc7

Update a Subscriber

ActionIn the docs only

Changes the details of a subscriber who is already in SimpleCirc, so a correction made in another tool reaches your circulation records too.

When to use it
a reader edits their profile in your CRM or support desk and SimpleCirc should follow.
Watch out
if Watch Events starts the same scenario, an update can raise a new event and restart the loop, so filter those out.
SimpleCirc8

Update a Subscription

ActionIn the docs only

Edits a subscription that already exists, which keeps the terms in SimpleCirc in line with what the reader agreed to elsewhere.

When to use it
a payment tool or a support ticket confirms a change to an existing subscription.
Watch out
point it at the exact subscription you mean, mapped from the module that created or found it, never a guess.
SimpleCirc9

Update an Address

ActionIn the docs only

Replaces an address already stored in SimpleCirc, so the next shipment goes where the reader actually lives now.

When to use it
a reader reports a move through a form, an email parser or your helpdesk.
Watch out
it changes an existing address; for a reader with none on file, start with Create an Address instead.
Need help

Need help automating SimpleCirc with Make?

A person reads every message.

FAQ

SimpleCirc and Make: common questions

01Is the SimpleCirc Make integration free?
Yes, on the Make side. SimpleCirc is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. You still need your own active SimpleCirc account, which SimpleCirc bills on its side.
02What do you need to connect SimpleCirc to Make?
An active SimpleCirc account and its API token. In SimpleCirc, open Account Settings, go to the API tab and copy the token. In Make, add a SimpleCirc module, click Create a connection, give it a name if you like, and paste the token. That connection is then reused by every SimpleCirc module in your scenarios, so you only do this once per account. Once saved, the connection shows up in the dropdown of any new SimpleCirc module you add later.
03Does the SimpleCirc Watch Events trigger fire instantly?
No. Watch Events is a scheduled trigger: Make checks SimpleCirc on the scenario's schedule, every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, and paid plans can go down to 1 minute. There is no instant trigger for SimpleCirc in Make, so an event waits until the next check. If timing matters, set the shortest interval your plan allows on the first module.
04What if a SimpleCirc module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SimpleCirc API with the same connection as the other modules, so you are not limited to the 10 listed ones. Keep in mind that the SimpleCirc documentation on Make says it is AI-generated and may contain mistakes, so check a module's behavior with Run once on a test record before trusting it with real subscribers. If a job only needs an existing module, prefer that module over a raw API call.
05Should you use Make or n8n for SimpleCirc?
It depends on what you need to automate. Make offers 10 SimpleCirc modules, from subscriber creation to address updates, plus Make an API Call for the rest, and it works on the Free plan. The same app often has an n8n node too, so check what that node covers before choosing. Compare the modules each tool gives you against the steps of your process, and pick the one that covers them with the least workaround. Both can link to the rest of your stack; the choice rests on coverage.
Same platform

Other docs you might need on this stack.

Browse all integrations