Resources · Make integration

Stood CRM Make integrationAutomate Stood CRM with Make.

Can Make feed your Stood CRM pipeline on its own? The Stood CRM Make integration gives you 2 modules: one trigger that watches deals and one action that submits a form. This guide shows sales and ops teams how to link the account and build a first working scenario.

Try the Stood CRM integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Stood CRM Make integration do?

The Stood CRM Make integration links your Stood CRM account to Make, a no-code tool where you build a scenario (an automation made of connected steps). Each step is a module: here, one watches your deals and one pushes form entries into your CRM, so data moves without copy and paste.

Leads that land in the CRM by themselves. Your prospects fill a form on another tool. Make picks up each entry and hands it to Submit Form, which relies on the Web Form API Key of your Stood CRM team. Nobody retypes a name or an email.

Deals that reach the rest of your team. Watch stood deals starts a scenario from your Stood CRM deals, so you can pass them to a spreadsheet, a chat channel or an invoicing app you already use in Make.

One entry point for every form. When your landing pages run on different tools, each one can feed the same Stood CRM team through a single action module.

Keep the scope in mind: Stood CRM has only these two modules in Make and no Make an API Call module, and the docs list neither fields nor limits for them. Make's own docs also flag their Stood CRM page as AI-generated content to verify. Before you commit, the Make review covers the tool as a whole, the n8n vs Make comparison helps if n8n is on your list, and the Make training takes you from zero to your own scenarios.

Connect

How do you connect Stood CRM to Make?

  1. 01

    Collect three values in Stood CRM

    You need an active Stood CRM account with access to Team Management. The docs have you copy the Function URL of the webFormSubmit function in the Firebase Console, the Team ID from your team card, then the API key from Generate under Web Form API Key.

  2. 02

    Open the connection window

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

  3. 03

    Paste your credentials and save

    Enter the values you copied from Stood CRM, or follow the instructions Make shows on screen. Once saved, the connection appears in the module and you can move on to its settings.

First scenario

Your first scenario with Stood CRM and Make

GoalWhen someone fills a form on another tool, Make sends the entry to Stood CRM with Submit Form.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the form tool your visitors already use as the starting point.

  2. 02

    Add Submit Form

    Click the + on the right of that first module, search for Stood CRM and choose Submit Form. Select your connection or click Create a connection if this is your first Stood CRM module.

  3. 03

    Map the form data

    Fill the Submit Form fields with data from the previous module: each answer from the form arrives as a bundle, one item passed from module to module, and you drop its values where Stood CRM expects them.

  4. 04

    Test with Run once

    Click Run once, then send a test entry through your form. Make runs the scenario one time and shows the bundles each module received, so you can check the entry reached Stood CRM.

  5. 05

    Schedule it and switch it on

    Open Scheduling on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Triggers

What starts a Stood CRM scenario

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

Stood CRM1Watch stood deals

Watch stood deals

triggerIn the docs only

Watch stood deals gives your scenario a starting point inside Stood CRM: your deals become bundles that the next modules can send elsewhere, to a sheet, a chat app or a billing tool. The docs do not say whether it returns new deals, updated deals or both, so check what arrives in your first test.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than that on the Free plan.
When to use it
when a deal logged by your sales team should show up in another tool without anyone copying it.
Watch out
the directory gives no description of this module and its type is inferred from its name, so run it once before building on it.
Modules

What Stood CRM can do in Make

Stood CRM gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Stood CRM1

Submit Form

ActionIn the docs only

Submit Form lets Make push an entry into Stood CRM as if a visitor had filled one of your web forms. It is the only action the app offers in Make.

When to use it
a prospect leaves details in another app of your scenario and belongs in Stood CRM.
Watch out
it depends on the Web Form API Key of your team, and the docs do not list its fields, so read them in the module after connecting.
Need help

Need help automating Stood CRM with Make?

A person reads every message.

FAQ

Stood CRM and Make: common questions

01Is the Stood CRM Make integration free?
Yes, on the Make side. Stood CRM is a standard app, so both of its modules work on 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) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one run of one module on one item. You still need your own Stood CRM subscription, which this page does not price.
02What do you need to connect Stood CRM to Make?
An active Stood CRM account with access to Team Management and a generated Web Form API Key. The docs have you collect three values: the Function URL of the webFormSubmit function in the Firebase Console, the Team ID shown on your team card, and the API key produced by the Generate button in the Marketing Source section. In Make, add a Stood CRM module, click Create a connection, name it if you like, and paste those values. The connection is then shared by both modules of the app.
03Does the Stood CRM trigger in Make work in real time?
No. Watch stood deals is a scheduled trigger: Make checks Stood CRM on the scenario's schedule instead of being called by the app. A new scenario runs every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans can go down to 1 minute. So a deal logged in Stood CRM reaches your other tools at the next check, not the second it is saved. Keep in mind the directory gives no description of this module and its type is inferred from its name.
04What if the Stood CRM module you need is missing in Make?
Then Make alone will not cover it. Stood CRM has just two modules, Watch stood deals and Submit Form, and no Make an API Call module to reach other parts of the app. The docs list no extra limits, and Make flags its Stood CRM page as AI-generated content that may contain mistakes, so check anything important with Stood CRM directly. If your process needs more, another app in your scenario may hold the data, or the team can help you look for a workable route.
05Should you use Make or n8n for Stood CRM?
It depends on what you check first. In Make, Stood CRM gives you a scheduled deal trigger and a form action, available from the Free plan, with a visual editor and a Run once test. Before comparing, confirm whether an n8n node exists for Stood CRM and which operations it covers, because this page only documents the Make side. Then compare the two on the modules your process actually needs, not on reputation: pick the tool where those modules already exist.
Same platform

Other docs you might need on this stack.

Browse all integrations