Use QuoteCloud with Make, bring your own
There's no ready-made QuoteCloud app on Make. Teams that build in Make connect with Make's built-in OAuth connection and call QuoteCloud's API or Zapier endpoints from their scenarios.
- 5/5 on G2
- 4.2 on Capterra
- Building QuoteCloud since 2013
Yes, QuoteCloud works with Make as a bring-your-own setup on the Essentials plan and up. You connect Make to QuoteCloud with Make's built-in OAuth connection, then call QuoteCloud's API or Zapier endpoints from a scenario, beside Make's own modules for the other app. There's no ready-made QuoteCloud app on Make.
Last reviewed by the QuoteCloud team
How does the Make set-up work?
Three parts. Only the first two involve QuoteCloud.
1. Make's OAuth connection
In Make, you set up its built-in OAuth connection to your QuoteCloud account, once. Scenarios then call QuoteCloud as that account.
2. QuoteCloud's API or Zapier endpoints
Each QuoteCloud step in a scenario is a call to QuoteCloud's API or to the endpoints behind its Zapier app: the same operations as the Zapier steps, such as creating a document or finding a contact.
3. Make's own modules for the other app
Make's modules for Google Sheets, your CRM, accounting or chat app handle the other side, as in any scenario.
Zapier or Make: what changes when you build it yourself
With Zapier, QuoteCloud's steps are ready-made: you pick Create Document or Document Signing Complete from a list and Zapier shows the fields.
With Make, you design each QuoteCloud call: which operation, which values, and how the scenario hears about QuoteCloud events. In return you get Make's own way of building, which suits teams that already run their automations there.
- Same QuoteCloud account and plan: Essentials and up
- Same rules: a scenario fills data items and price rows, never ticks the client's options or chooses content blocks
- Same short-lived PDF links: use them in the same run
Data items filled by the Zap
Site- Marlow House, levels 2–4From Google Sheets · Site
Floor area- 2,400 m²From Google Sheets · Floor area
Nights a week- 5From Google Sheets · Nights
Account manager- Theo VanceFrom Google Sheets · Owner
Build a QuoteCloud scenario in Make
- 1
Check the plan
QuoteCloud's API access is on Essentials and up; Make is a separate service with its own plans.
- 2
List the QuoteCloud steps
Write down each QuoteCloud operation the scenario needs, using the reference as the menu.
- 3
Set up the OAuth connection
In Make, set up its built-in OAuth connection to your QuoteCloud account. Ask QuoteCloud for the connection details.
- 4
Add the calls and modules
Add Make's modules for the other app, and a call to QuoteCloud's API or Zapier endpoints for each QuoteCloud step.
- 5
Test, then schedule
Run the scenario with a test record, check the document in QuoteCloud, then switch it on.
When is Make the better choice?
Choose Make when
Your team already builds in Make, the job needs branching or data handling that's easier in a scenario, or you want one tool for all your automations.
Choose Zapier when
A recipe on this site fits, you want ready-made QuoteCloud steps with their fields listed, or the person building it isn't a developer. Connect Zapier.
Want help scoping a Make build?
Start a free 14-day trial to try the API, or book a demo and talk through the scenario with QuoteCloud's team.
Make questions, answered
Does QuoteCloud have an app on Make?
No, not a ready-made one with listed modules. QuoteCloud supports Make as a bring-your-own setup: Make's built-in OAuth connection to your QuoteCloud account, then calls to QuoteCloud's API or Zapier endpoints from your scenario.
Which QuoteCloud plan does Make need?
Essentials or higher, the plan that includes QuoteCloud's API and Zapier access. Make itself is a separate service with its own plans.
Is there a per-document fee for documents a Make scenario creates?
Ask QuoteCloud. The per-document fee of US$2.00, $1.80 or $1.60 by volume is stated for documents created through Zapier or the API; for Make scenarios, confirm with QuoteCloud before you build for volume.
Can a Make scenario do everything a Zap can?
It reaches the same QuoteCloud operations, through QuoteCloud's API and Zapier endpoints, but you design each call yourself instead of picking a ready-made step. Talk to QuoteCloud about how your scenario should receive events such as a signature.
More on automating QuoteCloud
- QuoteCloud automation recipes for every appEvery QuoteCloud integration in one gallery: CRM, accounting, payments, field service, sheets, files and chat.
- Create QuoteCloud documents from other appsA new row, deal or form in another app drafts a QuoteCloud document from your template, filled in.
- Send QuoteCloud document events to other appsViewed, signed, paid, expired: each QuoteCloud event can update a CRM, file a PDF or tell the team.
- Connect QuoteCloud to Zapier, step by stepCheck the plan, connect QuoteCloud in Zapier, build the first Zap, test it and turn it on.
- Data items, price rows and images at creationWhat Create Document can fill: title, data items, price-table rows, recipients, images. What stays with people.
- Test and troubleshoot QuoteCloud ZapsTest with sample records, then fix the usual problems: no match found, expired links, empty rows.
- Who owns your QuoteCloud automationsWhich accounts the Zaps run as, who owns the documents they create, and how to keep a register.
- QuoteCloud Zapier triggers, actions and searchesAll 56 QuoteCloud Zapier events, searchable, with the fields each one takes and what it passes on.
- What automating QuoteCloud costsEssentials and up, plus a fee for each document a Zap or the API creates. Work it out for your volume.
- FAQAnswers to the questions teams ask before automating QuoteCloud with Zapier, Make or the API.
Build it your way, in Make.
Start a free 14-day trial of QuoteCloud and connect your first Make scenario to a test account.
Use QuoteCloud with MakeFree 14 days · no card
Start free trial