Resources · Make integration

Weavely Make integrationAutomate Weavely with Make.

New Weavely responses can start work on their own. The Weavely Make integration gives you 2 modules: a trigger that picks up responses and an API call for everything else. This guide connects your account and walks you through a first scenario.

Try the Weavely integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Weavely Make integration let you automate?

The Weavely Make integration links your Weavely account to Make, a visual tool where you chain apps together without writing code. Each automation you build there is a scenario, and each brick in it is a module. Weavely brings two of them: one that picks up new responses and one that calls the Weavely API directly.

Hand each new response to the rest of your stack. Watch Responses brings every new response into Make as a bundle, meaning one item passed from module to module. From there, the next module can be any of the 3,000+ standard apps Make offers on every plan, so a sales lead can land in your CRM and a support request in your helpdesk.

Reach what the listed modules leave out. Make an API Call reuses your Weavely connection to call any endpoint of the Weavely API. Keep the Weavely API documentation open to know which address to hit and what it returns.

Test before you trust it. The Run once button runs the scenario a single time and shows the bundles each module received, which is the fastest way to check a real response before switching anything on. The Make troubleshooting guide helps when a run fails.

What Make does not do here: there is no instant trigger for Weavely, so responses arrive on the scenario's schedule, not the moment they are submitted. Make's own documentation for this app is marked as AI-generated, so check important details against Weavely's documentation. If you are weighing tools, the n8n vs Make comparison lays out the choice, and the Make training takes you further.

Connect

How do you connect your Weavely account to Make?

  1. 01

    Copy your personal token

    Log in to Weavely and open your user profile or account settings. Find the section called Personal Token or API access and copy the API token shown there. You need an active Weavely account for this.

  2. 02

    Add a Weavely module

    In a Make scenario, add any Weavely module and click Create a connection. A connection is your Weavely account linked to Make once, then reused by every Weavely module you add later.

  3. 03

    Paste the token and save

    Give the connection a name in the Connection name field if you like; it is optional. Paste the token you copied, or follow the instructions Make shows on screen, then save the connection.

First scenario

Build your first scenario with Weavely

GoalWhen a new response lands in Weavely, Make picks it up and sends its data to a Weavely API endpoint you choose.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Add Watch Responses

    Search for Weavely, choose Watch Responses and click Create a connection with your personal token. Once connected, fill in the fields Make asks for.

  3. 03

    Add Make an API Call

    Click the + to the right of the trigger and pick Make an API Call. Point it at the Weavely endpoint you need and map values from the response the trigger delivered.

  4. 04

    Test with Run once

    Submit a test response in Weavely, then click Run once. Open each module's bubble to read the bundle it received and confirm the data is where you expect it.

  5. 05

    Schedule and switch it on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on so it keeps checking for responses without you.

Triggers

What starts a Weavely scenario?

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

Weavely1Watch Responses

Watch Responses

triggerIn the docs only

Watch Responses gives your scenario a steady feed of new Weavely responses, each arriving as its own bundle that the following modules can use. It is the only trigger this app offers, so almost every Weavely scenario starts here.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default, and never faster than 15 minutes on the Free plan.
When to use it
whenever a submitted response should set off work elsewhere, such as notifying a team or updating a record.
Watch out
each response that passes through a module counts as an operation, which is what Make bills against your plan.
Modules

What else can Make do with Weavely?

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

Weavely1

Make an API Call

ActionIn the docs only

Make an API Call opens the whole Weavely API to your scenario, using the same connection as Watch Responses, so you can reach an endpoint that no ready-made module covers.

When to use it
after Watch Responses, when you need something from Weavely that the trigger alone does not provide.
Watch out
you choose the endpoint and its data yourself, so keep Weavely's API documentation at hand.
Need help

Need help automating Weavely with Make?

A person reads every message.

FAQ

Weavely and Make: common questions

01Is the Weavely Make integration free?
Yes, on the Make side. Weavely is a standard app, so it works on the Free plan. That plan allows 2 active scenarios, a scheduled run no more often than every 15 minutes, up to 5 minutes 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. Your Weavely subscription is a separate matter; Weavely's own pricing page covers it.
02What is needed to connect Weavely to Make?
An active Weavely account and its personal token. You find the token in your Weavely user profile or account settings, in the section named Personal Token or API access. In Make, add a Weavely module, click Create a connection, optionally name it, and paste the token. The same connection then serves both Weavely modules, so there is nothing to repeat when you add Make an API Call later in the scenario. If the token ever changes, update the connection once and every module follows.
03Does the Weavely trigger in Make react in real time?
Most likely not. Make’s documentation does not state the type of Watch Responses; judging by its name, it is a scheduled trigger (check for the clock badge on the module): Make checks Weavely for new responses at the interval set on the scenario, which is every 15 minutes by default. On the Free plan that interval cannot go below 15 minutes; paid plans can go down to 1 minute. Weavely has no instant trigger in Make, meaning there is no webhook that would wake the scenario the moment a response is submitted. For most follow-up work, such as routing a response to another app, that delay is rarely a problem.
04What if a Weavely module is missing in Make?
Use Make an API Call. It reuses your Weavely connection and can call any endpoint of the Weavely API, which covers actions the two listed modules do not offer. You pick the endpoint and prepare the data yourself, so the Weavely API documentation is the reference to follow. Make's own page for this app is flagged as AI-generated and may contain mistakes, so confirm important details with Weavely directly. Test each call with Run once before switching the scenario on.
05Should Weavely be automated with Make or n8n?
It depends on the tool your team already works in. Make gives you Watch Responses and Make an API Call for Weavely, a visual editor and a Run once button to test each step. The same app often has an n8n node too, so check that side if n8n is already part of your stack. Neither answer is right for everyone; the n8n vs Make comparison linked earlier on this page sets the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations