Resources · Make integration

Qwilr Make integrationAutomate Qwilr with Make.

What happens in your stack the moment a client accepts a Qwilr proposal? The Qwilr Make integration gives you 6 modules: one instant trigger and 5 actions. This guide is for sales and ops teams, and it walks you from the connection to a first working scenario.

Try the Qwilr integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Qwilr Make integration do for you?

The Qwilr Make integration links your Qwilr account to Make, a no-code tool where you chain apps into a scenario, meaning the automation you build. Qwilr can tell Make the moment a page is accepted, and Make can create, read and update pages for you without anyone copying data by hand.

Kick off delivery the moment a deal closes. Watch Accepted Page fires when a client accepts a proposal. From there, a Create a Page with a Template module can build the onboarding page for that client, so the next document is ready before the account manager even opens their inbox.

Generate proposals from data you already hold. A row in a spreadsheet or a deal in your CRM can feed Create a Page with Blocks, which assembles a page piece by piece instead of starting from a fixed template. Sales reps stop rebuilding the same document for each prospect.

Keep pages in sync with the rest of your tools. Get a Page reads what a page holds, and Update a Page changes it when a price or a contact moves elsewhere. When you need something the listed modules skip, Make an API Call reaches the rest of the Qwilr API with the same connection.

Know the limits before you build. Qwilr offers a single trigger, for accepted pages, and no search module; anything outside the five actions goes through Make an API Call. The official documentation also warns that parts of it are AI-generated, so check anything critical against Qwilr itself. The same app often exists in n8n too, and the n8n vs Make comparison lays out the criteria. New to the tool? The Make training covers the basics, and the Make pricing page explains what each plan includes.

Connect

How do you connect your Qwilr account to Make?

  1. 01

    Generate an API key in Qwilr

    You need an active Qwilr account. In Qwilr, open Settings, go to the API tab and click Generate. Copy the key shown in the window that opens, because Make will ask for it in a moment.

  2. 02

    Add a Qwilr module in Make

    In your scenario, add any Qwilr module and click Create a connection. A connection is your Qwilr account linked to Make once, then reused by every Qwilr module. You can type a label in Connection name if you manage several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied from Qwilr, or follow the instructions Make shows on screen, then save. Make now lists what it can read from your account, and every other Qwilr module you add will offer this same connection.

First scenario

Your first scenario with Qwilr and Make

GoalWhen a client accepts a page in Qwilr, Make creates their onboarding page from a template.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Everything you build here starts from that single button.

  2. 02

    Add the Watch Accepted Page trigger

    Search for Qwilr and pick Watch Accepted Page. Click Create a webhook, then Create a connection with your API key. This module waits for Qwilr to announce each accepted page.

  3. 03

    Add Create a Page with a Template

    Click the + on the right of the trigger and choose Create a Page with a Template. Pick your onboarding template, then map data from the accepted page into the fields Make shows you.

  4. 04

    Test with Run once

    Click Run once, then accept a test page in Qwilr. Open each module's bubble to read the bundle it received, meaning the item that moved from one module to the next.

  5. 05

    Switch the scenario on

    When the test looks right, switch the scenario on. The trigger is instant, so Qwilr calls Make through the webhook each time a page is accepted, with no polling interval to set.

Triggers

What starts a Qwilr scenario?

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

Qwilr1Watch Accepted Page

Watch Accepted Page

Instant trigger

In Make“Triggers when a page is accepted.”

This trigger starts your scenario each time a client accepts one of your Qwilr pages, which usually means a signed proposal and a deal you can act on straight away. It is the only trigger Qwilr offers in Make, so every automated flow that begins inside Qwilr begins here.

How it fires
instant, since Qwilr calls Make through a webhook as soon as the page is accepted.
When to use it
you want onboarding, invoicing or a team alert to follow a won deal without anyone watching the Qwilr dashboard.
Watch out
it reacts to acceptance only, so edits or views on a page will not start anything.
Modules

What can Make do in Qwilr?

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

Qwilr1

Create a Page with a Template

Action

In Make“Creates a new page using a template.”

You get a new Qwilr page built on one of your saved templates, so every document keeps the layout your team already approved.

When to use it
a deal reaches a stage in your CRM and the matching proposal should exist without a rep copying a template by hand.
Watch out
the result is only as good as the template, so tidy it in Qwilr before you automate it.
Qwilr2

Create a Page with Blocks

Action

In Make“Creates a new page using blocks.”

Here the page is assembled from blocks you choose in the scenario, which gives you a document shaped by the data rather than by a fixed model.

When to use it
each prospect needs a different mix of sections, for example one pricing block per product they asked about.
Watch out
this route needs more setup than the template module, so start with the template one if a single layout fits.
Qwilr3

Get a Page

Action

In Make“Returns information about the page.”

This module hands your scenario the details of one existing page, so later modules can reuse what it contains instead of asking someone to look it up.

When to use it
right after Watch Accepted Page, when the next step needs more about the accepted page than the trigger itself delivered.
Watch out
it reads one page you already identify; Qwilr has no search module in Make to find pages by other criteria.
Qwilr4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you can reach any endpoint of the Qwilr API from your scenario, reusing the connection you already created, so nothing is out of reach just because no dedicated module exists.

When to use it
you need an operation the five other modules do not cover, such as an endpoint that has no module of its own in the list.
Watch out
you write the request yourself, so keep the Qwilr API reference open while you build it.
Qwilr5

Update a Page

Action

In Make“Updates the page.”

Update a Page changes a page that already exists, so your proposal keeps pace with what happens in your other tools without a manual edit.

When to use it
a contact or a price changes in your CRM after the proposal went out, and the page should reflect it.
Watch out
it changes a page your client may already be reading, so run it once on a test page before you point it at live proposals.
Need help

Need help automating Qwilr with Make?

A person reads every message.

FAQ

Questions about the Qwilr Make integration

01Is the Qwilr Make integration free?
Yes, on the Make side. Qwilr is a standard app, so it works from the Free plan, which gives you 2 active scenarios, a minimum of 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 lift the interval to 1 minute and remove the cap on active scenarios. Your Qwilr subscription is a separate matter, handled by Qwilr, and you still need an active account there.
02What do you need to connect Qwilr to Make?
An active Qwilr account and an API key. In Qwilr, open Settings, then the API tab, click Generate and copy the key. In Make, add a Qwilr module, click Create a connection, give it a name if you like and paste the key. If your first module is Watch Accepted Page, Make asks you to create a webhook first and the connection right after. That single connection then serves every Qwilr module in your scenarios.
03Does the Qwilr trigger in Make work in real time?
Yes. Watch Accepted Page is an instant trigger: Qwilr calls Make through a webhook as soon as a page is accepted, so your scenario starts right away instead of waiting for a polling interval. That also means the Free plan's minimum of 15 minutes between scheduled runs does not slow this trigger down. Keep in mind it is the only Qwilr trigger, so other events in Qwilr need another starting point, such as a trigger from a different app.
04What if a Qwilr module is missing in Make?
Use Make an API Call. It sends any request the Qwilr API accepts, with the connection you already set up, so you are not limited to the 5 action modules listed in Make. It is also the route for lookups, since Qwilr has no search module in Make. The Qwilr documentation in Make notes that part of it is AI-generated, so confirm the exact request against Qwilr's own reference before relying on it.
05Should you use Make or n8n for Qwilr?
It depends on the tool your team already runs. On Make, Qwilr brings 6 modules, including an instant trigger for accepted pages and a Make an API Call module for everything else, and it is available from the Free plan. The same app often has an n8n node too, so check what it offers for your use case. Compare the modules each side gives you for Qwilr rather than picking on reputation, and read the n8n vs Make comparison on this site for the wider picture.
Same platform

Other docs you might need on this stack.

Browse all integrations