Resources · Make integration

Gist Make integrationAutomate Gist with Make.

Your Gist contacts can update themselves while you work on something else. The Gist Make integration gives you 23 modules: 1 instant trigger, 16 actions and 6 searches. This page shows marketers and ops teams how to link the account, build a first scenario and pick the right module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Gist Make integration do for you?

The Gist Make integration links your Gist workspace to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Gist then creates, updates, tags and looks up your users and leads on its own, driven by what happens in your other apps.

Every form fill becomes a tagged lead. A contact form from another app starts the scenario, Create Lead adds the person to Gist and Tag/Untag Users or Leads files them under the right label, so your marketing team finds them in the right list without copying anything by hand.

Gist activity reaches the rest of your stack. Watch Events is an instant trigger: Gist calls Make through a webhook the moment an event fires, and your scenario can pull the full profile with Fetch User before passing it on.

Reports built from live Gist data. List Campaigns, List Segments and List Tracked Events return every matching item, one bundle at a time, ready to be sent to a sheet or a dashboard.

The official documentation gives no numbered limit for this app, and no prerequisite beyond a Gist account and its API key. When a listed module stops short, Make an API Call reaches any endpoint of the Gist API with the same connection. If you are still choosing a tool, read the n8n vs Make comparison, check Make pricing, or learn the editor step by step with the Make training.

Connect

How do you connect Gist to Make?

  1. 01

    Copy your API key in Gist

    Log in to Gist and open Settings, then API key. Click the Copy button: the key now sits in your clipboard. This key is what lets Make act on your workspace, so keep it out of shared documents.

  2. 02

    Open the connection dialog in Make

    Add any Gist module to your scenario and click Create a connection. A connection is your Gist account linked to Make once, then reused by every Gist module you add later, so you only do this step one time.

  3. 03

    Paste the key and confirm

    Paste the key into the API key field and click Continue. Make checks the key and saves the connection. From there, the module fields open up and you can start filling them.

First scenario

Your first scenario: turn form entries into tagged Gist leads

GoalWhen someone submits a form in another app, Make creates the lead in Gist and applies a tag to it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Pick the trigger of your form app: it hands each new entry to Make as a bundle, meaning one item that flows to the next module.

  2. 02

    Add Create Lead

    Click the + on the right of the form module, search for Gist and choose Create Lead. Click Create a connection if you have not linked the account yet, using the API key from the step above.

  3. 03

    Map the form data

    Fill the fields of Create Lead by clicking into them and picking the answers from the form module. Make shows the data it received, so you map the email to the email and the name to the name.

  4. 04

    Tag the new lead

    Add Tag/Untag Users or Leads after Create Lead. Point it at the lead the previous module returned and choose the tag to apply, for example the name of the campaign that brought the form.

  5. 05

    Test with Run once

    Click Run once, then submit a test entry in your form. Each module shows a bubble with the bundles it received: open them to check that the lead exists in Gist with its tag.

  6. 06

    Schedule and switch on

    Open the clock on the first module to set the schedule. A new scenario runs every 15 minutes by default, the shortest gap on the Free plan; an instant form trigger skips the wait. Then flip the scenario on.

Triggers

What starts a Gist scenario?

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

Gist1Watch Events

Watch Events

Instant trigger

In MakeResponds to events fired by Gist.

Watch Events gets your scenario moving the moment Gist fires an event, so the next modules work on fresh activity instead of waiting for a check. Every event arrives as one bundle you can map into the modules that follow, whether you want to enrich a profile, log the activity or alert someone.

How it fires
instant, Gist calls Make through a webhook as soon as the event happens, shown by the lightning badge on the module.
When to use it
when an action taken in Gist should start work somewhere else, like sending a profile to your CRM.
Watch out
if the scenario writes back into Gist, make sure that write cannot fire the same event again, or the scenario feeds itself.
Modules

What else can Gist do in Make?

Gist gives you 22 modules in 7 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Users

5 modules
Gist1

Create User

Action

In MakeCreates a new user.

Create User adds a new person to your Gist users, filled with the data your scenario already has, so a signup in your product shows up in Gist without anyone typing it again.

When to use it
when an account is opened in your app or a purchase is confirmed and that person should become a known user.
Watch out
for someone who is only a prospect, Create Lead fits better.
Gist2

Update User

Action

In MakeUpdates a user's details.

Update User changes the details of a user who already exists in Gist, so their profile keeps pace with what your billing tool or product says about them.

When to use it
after a plan change, a new company name or a corrected email coming from another app.
Watch out
it needs to know which user to change, so place Fetch User or List Users before it when you only have an email.
Gist3

Fetch User

Action

In MakeReturns a user.

Fetch User returns one user and their details, giving the rest of your scenario the full profile rather than the thin data that arrived with the trigger.

When to use it
right after Watch Events, when you need the name or attributes of the person behind the event before you send them elsewhere.
Watch out
it returns a single person; to go through many users, List Users is the right brick.
Gist4

List Users

Search

In MakeReturns a list of users.

List Users brings back your Gist users as separate bundles, which lets every following module run once per person without extra setup on your side.

When to use it
to export users to a spreadsheet or to check a whole group against another tool.
Watch out
a search can return zero, one or many bundles, and each module after it counts one operation, meaning one execution Make bills on your plan, per bundle.
Gist5

Delete User

Action

In MakeDeletes a user.

Delete User removes a user from Gist, which keeps your contact base clean when a person closes their account elsewhere or asks to be forgotten.

When to use it
when an account deletion in your product must be mirrored in Gist.
Watch out
a deletion cannot be rolled back from Make, so run tests on a dummy user first and add a filter that confirms the right person before this module.

Leads

5 modules
Gist6

Create Lead

Action

In MakeCreates a lead.

Create Lead records a new prospect in Gist, so a form answer, a chat or an imported list turns into a lead your team can follow up on.

When to use it
when the contact has not bought or signed up yet and you want to keep them apart from your users.
Watch out
the same form sent twice can create two leads; a List Leads check before this step avoids duplicates.
Gist7

Update Lead

Action

In MakeUpdates a lead's details.

Update Lead edits the details of an existing lead in Gist, so new information gathered after the first contact lands on the right record rather than in a note somewhere.

When to use it
after a second form, a call booked in your calendar tool or a reply that adds a phone number.
Watch out
you must point it at a lead that exists, often the one returned by Fetch Lead.
Gist8

Fetch Lead

Action

In MakeReturns a lead.

Fetch Lead retrieves one lead with its details, so the modules that follow can read who this prospect is before deciding anything about them.

When to use it
when a scenario receives only an identifier and you need the full record to route the prospect to the right salesperson.
Watch out
this module reads a single lead; for a batch of prospects, use List Leads and let each bundle flow on.
Gist9

List Leads

Search

In MakeReturns a list of leads.

List Leads returns your leads one bundle at a time, which gives you a simple way to review or move a group of prospects in a single run.

When to use it
before Create Lead to see whether a contact already exists, or to copy leads into a sales sheet.
Watch out
when the search finds nothing, the next modules do not run, so test with a known contact to be sure your filter matches.
Gist10

Delete Lead

Action

In MakeDeletes a lead.

Delete Lead wipes a lead from Gist, useful when a prospect becomes a user elsewhere or turns out to be a test entry you never wanted in your base.

When to use it
after a cleanup step that marks spam or duplicate leads coming from a public form.
Watch out
nothing brings the lead back once Make has run the module, so keep a copy with another app first if the history matters to you.

Tags

5 modules
Gist11

Create Tag

Action

In MakeCreates a tag.

Create Tag adds a new label to your Gist workspace, so a scenario can prepare the tag it needs instead of failing because nobody created it by hand.

When to use it
when a new campaign, product or event starts in another tool and its contacts need their own tag in Gist.
Watch out
run List Tags first if the tag may already exist, to avoid two labels with the same meaning.
Gist12

Update Tag

Action

In MakeUpdates a tag.

Update Tag renames or edits a tag that already exists, so your labels stay consistent with how the team talks about a campaign or a customer group today.

When to use it
when a product is renamed or a campaign changes its title in the tool where it is managed.
Watch out
every contact carrying the tag sees the change, so check who uses it before editing.
Gist13

Tag/Untag Users or Leads

Action

In MakeTags or untags a list of users and/or leads.

Tag/Untag Users or Leads puts a tag on a list of users and leads, or takes it off, which is how a scenario sorts your contacts into the right segments without manual clicks.

When to use it
after a purchase, a webinar signup or a cancellation that should move someone in or out of a group.
Watch out
the same module both adds and removes, so double check which of the two your setting asks for before you switch the scenario on.
Gist14

List Tags

Search

In MakeReturns a list of all tags.

List Tags returns every tag of your workspace, each as its own bundle, so your scenario can check what exists before creating or applying anything.

When to use it
to feed a dropdown in another tool, or to confirm a tag is there before Tag/Untag Users or Leads runs.
Watch out
each tag becomes a bundle, so add a filter if only one of them matters for the rest of the flow.
Gist15

Delete Tag

Action

In MakeDeletes a tag.

Delete Tag removes a label from Gist altogether, handy to keep your tag list short once a campaign is over and its label only adds noise.

When to use it
when a campaign is archived in your project tool and its tag should disappear with it.
Watch out
the tag leaves every contact that carried it, and Make cannot restore it, so check with the team that nobody filters on it.

Segments

2 modules
Gist16

Fetch Segment

Action

In MakeReturns a segment.

Fetch Segment returns one of your Gist segments and its details, so a scenario can read how a group of contacts is defined before reporting on it.

When to use it
when a report or an alert concerns one specific segment, such as trial users you already built in Gist.
Watch out
segments are read here, not changed; to move people between groups, work with tags instead.
Gist17

List Segments

Search

In MakeReturns a list of segments.

List Segments brings back all your segments as separate bundles, a quick way to get an overview of how your audience is split without opening Gist.

When to use it
to copy the segment list into a sheet the marketing team reviews, or to pick one segment before Fetch Segment.
Watch out
modules placed after it run once per segment, which adds operations to your plan.

Campaigns

2 modules
Gist18

Fetch Campaign

Action

In MakeReturns a campaign.

Fetch Campaign reads one campaign from Gist with its details, giving your scenario what it needs to share the campaign status with people outside Gist.

When to use it
when a message to your team chat or a row in a report should describe one campaign in particular.
Watch out
it only reads the campaign; no listed module sends or edits one, so look at Make an API Call if the Gist API offers it.
Gist19

List Campaigns

Search

In MakeReturns a list of campaigns.

List Campaigns returns your Gist campaigns, one bundle each, so you can build a single view of them in the tool your managers already open.

When to use it
to fill a reporting sheet or a dashboard with every campaign and its details.
Watch out
with many campaigns, each following module counts one operation per bundle; aggregate them into a single row set if your plan is tight.

Tracked Events

2 modules
Gist20

Record Tracked Event

Action

In MakeRecords a tracked event.

Record Tracked Event writes an event on a contact in Gist, so something that happened in another tool, like a payment or a demo booked, becomes part of that contact's history.

When to use it
when activity outside your website should count in Gist, for instance an invoice paid in your billing app.
Watch out
if Watch Events listens to the same kind of event, check the scenarios do not trigger each other.
Gist21

List Tracked Events

Search

In MakeReturns a list of tracked events.

List Tracked Events returns the tracked events stored in Gist, one per bundle, so you can analyze or archive the activity of your contacts in another tool.

When to use it
to feed a spreadsheet or a data tool with the actions your contacts took, for a report the product team reads.
Watch out
a long history turns into many bundles, so filter right after this module to keep only what the report needs.

Other

1 module
Gist22

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call sends any request to the Gist API with the connection you already set up, so you are not stuck when the listed modules stop short of what you need.

When to use it
for a Gist feature that none of the other modules covers, once you have found the endpoint in the Gist API reference.
Watch out
you write the request yourself, so test it with Run once and read the response before switching the scenario on.
Need help

Need help automating Gist with Make?

A person reads every message.

FAQ

Gist and Make: frequent questions

01Is the Gist Make integration free?
Yes. Gist is a standard app in Make, available from the Free plan, like the 3000 or more standard apps on every plan. The Free plan still has limits: 2 active scenarios, at least 15 minutes between two 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) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, meaning operations, each month. Your Gist subscription is a separate matter that Make does not handle.
02What do you need to connect Gist to Make?
A Gist account and its API key, nothing more according to the official documentation. In Gist, go to Settings, then API key, and click Copy. In Make, open any Gist module, click Create a connection, paste the key in its field and click Continue. The connection is saved once and every Gist module in your scenarios reuses it. If you manage several Gist workspaces, create one connection per workspace and give each a clear name, so you always know which account a scenario writes to.
03Does the Gist trigger in Make react in real time?
Yes. Watch Events is an instant trigger: Gist calls Make through a webhook as soon as the event fires, and the module shows a lightning badge rather than a clock. Your scenario therefore starts on the event itself, not on a 15 minute schedule. The other Gist modules are actions and searches, so they only run when something upstream starts the scenario, either this trigger or the trigger of another app. For a scenario that starts from another tool, the timing depends on that tool's trigger, instant or scheduled.
04What if a Gist module is missing in Make?
Use Make an API Call. This module sends a request to any endpoint of the Gist API with the connection you already created, so you can cover what the other modules do not, such as an action on a campaign, which the listed modules only read, provided the Gist API exposes it. You need to know the endpoint and the data to send, which comes from the Gist API reference. The official Make documentation for Gist gives no numbered limit, so there is no quota to plan around from that side. Test every custom call with Run once before activating.
05Should you use Make or n8n for Gist?
It depends on the tool you already run, not on Gist itself. Many apps that exist in Make also have an n8n node, so check the n8n catalog for Gist before deciding. On Make you get 23 ready modules, including an instant trigger and Make an API Call for the rest, and you can start on the Free plan. If your team already builds its automations in n8n, keeping Gist there avoids splitting your flows across two tools. The comparison page linked above details how the two platforms differ, without any cost ranking between them.