Resources · Make integration

Content Snare Make integrationAutomate Content Snare with Make.

Stop chasing clients for files by hand. The Content Snare Make integration gives you 44 modules, including 18 instant triggers, to react when a request moves forward. This guide is for agencies and accountants who collect client content, and it walks you through your first scenario.

Try the Content Snare integration on MakeSee the 44 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Content Snare Make integration do for you?

The Content Snare Make integration links your Content Snare account to Make so that clients, requests and fields can drive a scenario, which is the automation you build in Make as a chain of modules. A module is one brick of that chain: a trigger that starts it, an action that changes something, or a search that reads a list. No code is needed.

Onboard a client with one event. Watch New Clients fires when someone is added to Content Snare, and Create a Request prepares the questionnaire for them right away. Nobody has to remember to send it.

Close the loop when the content is in. Watch Completed Requests tells Make that a client has answered everything. From there, Get a Request pulls the full request and the next module can hand it to your project tool, your drive or your inbox.

Keep the review moving. Watch Rejected Fields and Watch Approved Fields follow each decision on a field, while Review a Field and Approve All Submitted Fields let a scenario take those decisions itself once your own checks pass.

Every trigger of this app is instant: Content Snare calls Make through a webhook, so there is no polling clock to set. What Make does not give you is a module for every screen of the app; anything missing goes through Make an API Call with the same connection. The same app often has an n8n node too, and the n8n vs Make page helps you pick. Before you scale up, read Make pricing to see how operations are counted, and Make training if you are new to the editor.

Connect

How do you connect Content Snare to Make?

  1. 01

    Add a Content Snare module

    Log in to Make, open your scenario and add any Content Snare module. Then click Create a connection. A connection is your Content Snare account linked to Make once, and every module of the app reuses it afterwards.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name such as the workspace or the client team helps later, when several people share the same Make organization and pick connections from a list.

  3. 03

    Paste your credentials

    Enter the credentials you copied from Content Snare, or follow the instructions Make shows on screen. You need an active Content Snare account and an API key. For your own OAuth app, open your avatar, then Settings, then API under Integrations, and click Create a New Application.

First scenario

Your first scenario: send a request to every new client

GoalWhen a new client is created in Content Snare, Make creates a request for that client.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module on the empty canvas.

  2. 02

    Add Watch New Clients

    Search for Content Snare, pick Watch New Clients, click Create a webhook and then Create a connection to link your account, as described above.

  3. 03

    Add Create a Request

    Click the + on the right of the trigger and choose Create a Request. Fill its fields and map the client from the trigger, so each new client gets a request of their own.

  4. 04

    Test with Run once

    Click Run once, then add a test client in Content Snare. Open the bubble above each module to read the bundle it received and check that the request was created for the right person.

  5. 05

    Switch it on

    Save and turn the scenario on. Since the trigger is instant, Content Snare calls Make the moment a client is added, and every run counts one operation per module on your plan.

Triggers

Content Snare triggers: what starts your scenario

18 modules start a scenario when something happens in Content Snare. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Content Snare as soon as it happens.

Content Snare1Watch Added Comments

Watch Added Comments

Instant trigger

In Make“Triggers when a comment is added.”

Each comment posted on a request reaches your scenario as a bundle, which is one item handed from a module to the next. A question from a client stops sitting unnoticed inside Content Snare while your team works elsewhere.

How it fires
instant, Content Snare calls Make through a webhook as soon as the comment is added.
When to use it
your account managers answer from a shared inbox or a chat tool and need each comment forwarded there.
Watch out
every comment is its own bundle, so a lively request can start many runs; filter in the next module.
Content Snare2Watch All Fields Completed

Watch All Fields Completed

Instant trigger

In Make“Triggers when all the fields are completed.”

Here the signal is the finish line of the questionnaire: the scenario starts only once every field has an answer, not at each field. That keeps downstream tools quiet until there is something complete to look at.

How it fires
instant, the app calls Make by webhook the moment the last field is filled.
When to use it
a copywriter or a bookkeeper should start working only when the whole set of answers is available.
Watch out
completed does not mean approved; pair it with the review modules if a check has to happen first.
Content Snare3Watch Approved Fields

Watch Approved Fields

Instant trigger

In Make“Triggers when a field is approved.”

Approval of a single field becomes a starting point, which lets you act on validated answers one by one instead of waiting for the full request. Good for long questionnaires where some parts unlock work early.

How it fires
instant, Content Snare notifies Make through a webhook when someone approves the field.
When to use it
the logo or the legal text is approved and the designer or the lawyer can start without waiting for the rest.
Watch out
one request can send many bundles, one per approved field, and each run uses operations.
Content Snare4Watch Archived Requests

Watch Archived Requests

Instant trigger

In Make“Triggers when a request is archived.”

Archiving is usually the last gesture on a project, and this trigger turns it into a clean handoff: the scenario learns that a request is closed and can tidy up everything linked to it in your other tools.

How it fires
instant, the app calls Make by webhook as soon as the request is archived.
When to use it
you want the matching project card, folder or deal marked as done at the moment the request leaves your active list.
Watch out
archived is not deleted, so keep this apart from Watch Deleted Requests in your logic.
Content Snare5Watch Completed Fields

Watch Completed Fields

Instant trigger

In Make“Triggers when a field is completed.”

With this one, your scenario hears about progress field by field, the moment a client fills in an answer. It gives you a live picture of how far a questionnaire has moved without opening Content Snare.

How it fires
instant, Content Snare calls Make through a webhook right after the field is completed.
When to use it
a specific answer, such as a billing address, has to be copied into your CRM as soon as it exists.
Watch out
a large request produces many runs; if you only care about the end, Watch All Fields Completed is lighter on operations.
Content Snare6Watch Completed Requests

Watch Completed Requests

Instant trigger

In Make“Triggers when a request is completed.”

The whole request is done: that is the moment this trigger reports to Make. It is the natural start for anything that should follow a finished client file, from a thank-you message to the next project step.

How it fires
instant, the app notifies Make by webhook as soon as the request is marked complete.
When to use it
an agency moves a website project to production once the client has delivered every text and image.
Watch out
add Get a Request after it when later modules need the full content of the request.
Content Snare7Watch Deleted Clients

Watch Deleted Clients

Instant trigger

In Make“Triggers when a client is deleted.”

Removing a client in Content Snare can clean up after itself elsewhere, because this trigger passes the deletion to your scenario. Your other lists stop holding people who no longer exist in the app.

How it fires
instant, Content Snare calls Make through a webhook at the moment the client is deleted.
When to use it
a mailing list or a shared spreadsheet mirrors your Content Snare clients and must stay in step.
Watch out
the deletion is already done in Content Snare, so build the cleanup from what the bundle carries and check it with Run once.
Content Snare8Watch Deleted Requests

Watch Deleted Requests

Instant trigger

In Make“Triggers when a request is deleted.”

When a request disappears for good, Make gets told, so the tasks, folders or reminders you built around it do not linger. It is housekeeping that no one has to remember.

How it fires
instant, the app sends a webhook to Make as soon as the request is deleted.
When to use it
a project management board holds one card per request and orphan cards keep piling up.
Watch out
make the cleanup step cautious, since a deletion in your other tool is often just as final as the one in Content Snare.
Content Snare9Watch Deleted Team Members

Watch Deleted Team Members

Instant trigger

In Make“Triggers when a team member is deleted.”

Offboarding gets one step simpler: as soon as a colleague is removed from Content Snare, the scenario receives the event and can take the same person out of the other tools your team shares.

How it fires
instant, Content Snare calls Make by webhook when the team member is deleted.
When to use it
an ops manager keeps a staff directory or access list that should mirror who works in Content Snare.
Watch out
the removal is already done in Content Snare; the scenario only mirrors it, so test the cleanup with Run once.
Content Snare10Watch New Clients

Watch New Clients

Instant trigger

In Make“Triggers when a new client is created.”

A fresh client record is often the start of everything else, and this trigger hands it to Make right away so onboarding can begin without anyone copying details between apps.

How it fires
instant, the app calls Make through a webhook as soon as the client is created.
When to use it
every new client should get a request, a CRM contact or a welcome email, as in the first scenario above.
Watch out
if another scenario also creates clients through Create a Client, each creation fires this trigger too, so avoid scenarios that feed each other.
Content Snare11Watch New Requests

Watch New Requests

Instant trigger

In Make“Triggers when a new request is created.”

Any request created in the account, by hand or by another scenario, shows up in Make as a new bundle. That gives you one place to log, count or announce every questionnaire that starts.

How it fires
instant, Content Snare notifies Make by webhook the moment the request is created.
When to use it
a project lead wants a matching task opened in the team tool whenever a request is drafted.
Watch out
creation and publication are two separate events; if the client should already hold it, Watch Published Requests is the better signal.
Content Snare12Watch New Team Members

Watch New Team Members

Instant trigger

In Make“Triggers when a new team member is created.”

Adding a colleague to Content Snare can set up the rest of their access in the same breath. The scenario receives the new team member and passes the details to your HR or IT tools.

How it fires
instant, the app calls Make via webhook as soon as the member is created.
When to use it
a studio onboarding a freelancer wants the same person added to the shared drive and the chat workspace.
Watch out
Create a Team Member in another scenario also fires this trigger, which is expected but worth knowing before you chain them.
Content Snare13Watch Published Requests

Watch Published Requests

Instant trigger

In Make“Triggers when a request is published.”

Publishing is when a request goes out to the client, and this trigger catches that exact step. Your scenario can then start a follow-up sequence that matches what the client actually received.

How it fires
instant, Content Snare calls Make through a webhook once the request is published.
When to use it
a sales team logs in the CRM that the questionnaire has been sent, so nobody asks the client twice.
Watch out
a request published by another scenario fires it too, so keep one scenario in charge of sending follow-ups.
Content Snare14Watch Rejected Fields

Watch Rejected Fields

Instant trigger

In Make“Triggers when a field is rejected.”

A rejected answer means the client has more work to do, and this trigger surfaces it immediately so the person in charge can follow up with context rather than discover it days later.

How it fires
instant, the app sends Make a webhook as soon as the field is rejected.
When to use it
an account manager wants a direct message whenever a client file is sent back, to call the client personally.
Watch out
a strict reviewer can reject several fields in a row, and each rejection starts its own run.
Content Snare15Watch Updated Clients

Watch Updated Clients

Instant trigger

In Make“Triggers when a client is updated.”

Changes to a client record travel to Make as they happen. Your CRM or invoicing tool stops drifting away from what Content Snare holds.

How it fires
instant, Content Snare calls Make by webhook when the client is updated.
When to use it
the finance team invoices from another app and needs the latest client details there.
Watch out
if your scenario writes back to Content Snare with Update a Client, it fires this trigger again and can loop.
Content Snare16Watch Updated Kanban Column

Watch Updated Kanban Column

Instant trigger

In Make“Triggers when a kanban column is updated.”

Your kanban board in Content Snare becomes a control panel: moving work between columns can drive what happens in other tools, since this trigger reports each change to a column.

How it fires
instant, the app calls Make through a webhook as soon as the column is updated.
When to use it
the team already manages requests on the board and wants the stages mirrored in a reporting sheet.
Watch out
test with Run once to see what the bundle contains before relying on a column name in later modules.
Content Snare17Watch Updated Requests

Watch Updated Requests

Instant trigger

In Make“Triggers when a request is updated.”

Any edit to a request is pushed to your scenario. It suits anyone who tracks requests in a second tool and wants that copy to stay accurate.

How it fires
instant, Content Snare notifies Make by webhook the moment the request is updated.
When to use it
a project board shows one card per request and should reflect each change made in Content Snare.
Watch out
Update a Request in the same scenario fires this trigger again; keep writes and watches in separate flows.
Content Snare18Watch Updated Team Members

Watch Updated Team Members

Instant trigger

In Make“Triggers when a team member is updated.”

Changes to a colleague profile on your side of the account reach Make as they happen. Other tools that list your staff can follow without manual edits.

How it fires
instant, the app calls Make via webhook as soon as the team member is updated.
When to use it
an internal directory or a routing rule in your helpdesk depends on who does what in Content Snare.
Watch out
Update a Team Member placed later in the same scenario triggers it again, so avoid that pairing.
Modules

Content Snare actions and searches: what Make can do in the app

Content Snare gives you 26 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Content Snare1

Approve All Submitted Fields

Action

In Make“Approves all submitted for review fields in a request.”

One step clears the whole review queue of a request: every field the client submitted for review becomes approved at once.

When to use it
your own check has already passed elsewhere, for example a form in another tool, and clicking each field would be busywork.
Watch out
it approves everything submitted, so place it after a condition you trust.
Content Snare2

Create a Client

Action

In Make“Creates a new client.”

A new contact lands in Content Snare without retyping, fed by whatever app first captured the person, such as a signed quote or a booking form.

When to use it
a deal is won in your CRM and the client should exist in Content Snare before any request is sent.
Watch out
it fires Watch New Clients too, which is fine unless that trigger also creates clients.
Content Snare3

Create a Page

Action

In Make“Creates a new page.”

Adds a new page to a request, so a questionnaire can grow with the project instead of being rebuilt from scratch in the app.

When to use it
a client buys an extra service and the request needs a dedicated page to collect the matching content.
Watch out
List Page Templates tells you which templates exist before you build the page.
Content Snare4

Create a Request

Action

In Make“Creates a new request.”

Sends work to the client side of Content Snare by preparing a full request from your scenario, the heart of most onboarding flows.

When to use it
a new client appears, a contract is signed or a project starts in another tool, and the questionnaire should follow on its own.
Watch out
run List Request Templates first if you are not sure which template to pick.
Content Snare5

Create a Section

Action

In Make“Creates a new section.”

Inserts a section inside a request, a finer grain than a page, handy for grouping a few extra questions where they belong.

When to use it
an option on the order form means a handful of new questions must appear in the existing request.
Watch out
List Section Templates shows the reusable blocks already saved in your account.
Content Snare6

Create a Team Member

Action

In Make“Creates a new team member.”

Gives a new colleague a seat in Content Snare from the tool where you manage people, so access is ready on the first day.

When to use it
an HR or IT app records a hire and Content Snare should be part of the standard setup.
Watch out
it also fires Watch New Team Members, keep that in mind if both live in your account.
Content Snare7

Delete a Client

Action

In Make“Deletes a client.”

Removes a client record from Content Snare, the tidy end of a relationship that has closed in your main system.

When to use it
a client is marked lost or inactive in the CRM and should vanish from the Content Snare list too.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a dummy record first.
Content Snare8

Delete a Request

Action

In Make“Deletes a request.”

Erases a request completely, which keeps the account free of tests, duplicates and projects that never started.

When to use it
a deal falls through before kick off and the prepared questionnaire should not reach the client.
Watch out
archiving may be what you want instead; a deleted request and its answers do not come back.
Content Snare9

Delete a Team Member

Action

In Make“Deletes a team member.”

Takes a person out of your Content Snare team as part of an offboarding flow started in your HR or IT tool.

When to use it
a contract ends and every workspace account of that person must close on the same event.
Watch out
Make cannot undo the removal, so test it with Run once on a dummy member first.
Content Snare10

Get a Client

Action

In Make“Returns a client with a specific ID.”

Reads one client by its ID and returns the full record, useful when a trigger only hands you a reference.

When to use it
a comment or a request event arrives and the next module needs the client details to address them.
Watch out
it needs an ID; when you only know a name, List Clients is the module to reach for.
Content Snare11

Get a Request

Action

In Make“Returns a request with a specific ID.”

Fetches a single request by ID with its details, so later modules work from the current state rather than the short event data.

When to use it
right after Watch Completed Requests, to hand the full answers to a drive, a document tool or a project board.
Watch out
without an ID from an earlier module, use List Requests to find the request first.
Content Snare12

Get a Team Member

Action

In Make“Returns a team member with a specific ID.”

Returns one colleague by ID, which turns a bare reference in a bundle into a person you can notify or credit.

When to use it
an event mentions who owns a request and you want to message that owner directly.
Watch out
it looks up one member only; List Team Members covers the whole team.
Content Snare13

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Content Snare API with the connection you already set up, for the cases none of the listed modules covers.

When to use it
you need an operation of the app that has no module of its own in Make.
Watch out
you write the request yourself, so read the Content Snare API docs before adding it to a live scenario.
Content Snare14

Review a Field

Action

In Make“Approves or rejects a field.”

Records a decision on one field, approved or rejected, without anyone opening the review screen.

When to use it
a checker in another tool validates a document, for instance a file that must be signed, and the result should land in Content Snare.
Watch out
a rejection fires Watch Rejected Fields, so plan who follows up.
Content Snare15

Review an Answer

Action

In Make“Rejects or approves an answer (For multi answer fields).”

Works on a single answer inside a field that accepts several, approving or rejecting it while leaving the other answers untouched.

When to use it
a client uploads several photos or references in one field and only one of them misses the mark.
Watch out
for fields with a single answer, Review a Field is the right module.
Content Snare16

Submit All Fields For Review

Action

In Make“Submits all fields in request for review.”

Pushes every field of a request into review in one go, so the reviewer gets a complete batch instead of a trickle.

When to use it
Watch All Fields Completed fires and you want the whole request queued for your team straight after.
Watch out
it submits all fields, including ones you may prefer to review later.
Content Snare17

Update a Client

Action

In Make“Updates a client.”

Changes the details of an existing client, keeping Content Snare in line with the system where client data really lives.

When to use it
a contact's details change in your CRM and Content Snare should show the same thing.
Watch out
this fires Watch Updated Clients; a scenario that listens and writes to the same client can loop.
Content Snare18

Update a Request

Action

In Make“Updates a request.”

Edits a request already in place, for example to change its details when the project it belongs to moves on.

When to use it
the project changes in your project board and the client request should say the same thing.
Watch out
each change fires Watch Updated Requests, so keep this away from a scenario that listens to it.
Content Snare19

Update a Team Member

Action

In Make“Updates a team member.”

Keeps a colleague profile current in Content Snare when the change starts in your HR or directory tool.

When to use it
someone's details change in your HR tool and the team list in Content Snare should reflect it on the same event.
Watch out
it triggers Watch Updated Team Members, avoid chaining the two in one flow.
Content Snare20

List Clients

Search

In Make“Returns a list of clients.”

Returns your clients as a series of bundles, zero, one or many, so a scenario can go through them one by one.

When to use it
you need to find a client without knowing the ID, or copy the full client list to a sheet.
Watch out
each bundle it returns can run every later module, which adds operations quickly.
Content Snare21

List Communication Templates

Search

In Make“Returns a list of communication templates.”

Shows the message templates saved in your Content Snare account, handy for checking what is available before automating anything around them.

When to use it
you are building a request flow and want to see which communication templates exist in the account.
Watch out
this is a read step; it sends nothing to clients.
Content Snare22

List Page Templates

Search

In Make“Returns a list of page templates.”

Brings back the page templates of the account, a quick inventory before a scenario builds pages with Create a Page.

When to use it
different services need different pages and the scenario must pick the matching template.
Watch out
it can return several bundles, so place it where a list makes sense in the flow.
Content Snare23

List Requests

Search

In Make“Returns a list of requests.”

Lists the requests of the account, which is how a scenario finds one when no trigger has handed over its ID.

When to use it
a status report or a spreadsheet of all open questionnaires has to be built on demand.
Watch out
an empty result is possible; plan what the next module does with zero bundles.
Content Snare24

List Request Templates

Search

In Make“Returns a list of request templates.”

Gives you the request templates saved in Content Snare, the menu from which Create a Request usually picks.

When to use it
the service sold decides which questionnaire goes out, and the scenario must match one to the other.
Watch out
run it with Run once first to see what each bundle holds before you map it.
Content Snare25

List Section Templates

Search

In Make“Returns a list of section templates.”

Reads the reusable section templates of your account, the building blocks you can drop into a request with Create a Section.

When to use it
an add-on option should insert a known set of questions into the existing request.
Watch out
it only reads templates; nothing changes in your requests.
Content Snare26

List Team Members

Search

In Make“Returns a list of team members.”

Returns everyone on your Content Snare team as separate bundles, a simple way to audit who has access.

When to use it
an ops lead compares the Content Snare team with the HR list to spot accounts that should close.
Watch out
with a large team, every later module runs once per member and uses operations.
Need help

Need help automating Content Snare with Make?

A person reads every message.

FAQ

Content Snare and Make: common questions

01Is the Content Snare Make integration free?
Yes, on the Make side: Content Snare is a standard app, available from the Free plan. That plan gives you 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 transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations each month, one per module per bundle. You still need your own Content Snare subscription, which this page does not price.
02What do you need to connect Content Snare to Make?
You need an active Content Snare account and an API key. In Make, add any Content Snare module, click Create a connection, optionally name it, then enter the credentials copied from Content Snare or follow the steps shown on screen. With an instant trigger, click Create a webhook first. If you register your own OAuth application, go to your avatar, Settings, then API under Integrations, click Create a New Application, paste the Make callback URI and copy the Client ID and Client secret.
03Do Content Snare triggers in Make react in real time?
Yes. All 18 Content Snare triggers are instant: the app calls Make through a webhook as soon as the event happens, whether a comment is added, a field is approved or a request is completed. You do not wait for the 15 minute default schedule that applies to polling triggers. Each trigger carries the lightning badge in the editor, and Make asks you to create a webhook when you add one. The scenario still has to be switched on for events to be processed.
04What if a Content Snare module is missing in Make?
Use Make an API Call. It calls any endpoint of the Content Snare API with the connection you already have, so you are not limited to the 19 actions and 7 searches listed on this page. You write the request yourself from the Content Snare API documentation, then test it with Run once. The Make documentation for this app also warns that its content is AI generated from vendor docs and may hold mistakes, so check important details with Content Snare directly.
05Should you use Make or n8n for Content Snare?
It depends on the tool your team already uses. On Make, Content Snare comes with 44 ready modules, including 18 instant triggers, and the editor explains each step visually, which suits someone building their first automation. The same app often has an n8n node as well, so check what it covers for your case before choosing. Pick the platform where your other scenarios already run, since connections and habits carry over, and compare the two on the modules you actually need.
Same platform

Other docs you might need on this stack.

Browse all integrations