Quanda and Make: connect emails to your CRM and other apps

Make (formerly Integromat) is a platform that connects Quanda with hundreds of other apps without code: your CRM, online store, payment gateway, calendar, helpdesk and Google Sheets. Quanda, an email marketing and marketing automation platform, has its own verified app in Make with 12 modules. You can transfer contacts and companies to Quanda automatically, add tags to them, send a transactional email, and automations in Quanda take care of the next steps.

At a glance

1. Make connects Quanda with apps it has no direct integration with, and it does so without code.
2. Quanda has 12 modules in Make: 9 actions and 3 search modules. The app is managed directly by Quanda.
3. The most common scenario: a new customer in another app appears in Quanda with a tag, and the tag starts an automation.
4. You send individual emails via Make as transactional emails, including an attachment and custom variables.
5. You react to events in Quanda, such as an opened email or a completed survey, through webhooks.
6. You set up your first scenario in 6 steps: API key, new scenario, Quanda module, field mapping, test and scheduling.

In short: what the Make integration can do, what you need and when to choose another route

• What it can do: transfer contacts and companies, manage tags, send transactional emails and read sent campaigns.
• What you need: a Make account (the free plan is enough) and an API key from Quanda.
• Who sets it up: you can do it yourself, the scenario is built with your mouse. We are happy to help with your first scenario.
• When to choose another route: Raynet and Pipedrive have a ready direct integration, and Quanda HUB covers ERP, DMS and documents.

What has changed since publication: The article was first published in August 2021 under the title Connect Quanda with hundreds of other apps, when Make was still called Integromat. In October 2026 we rewrote it for the current Quanda app in Make, which now has twelve modules instead of the original three. We added a step by step guide, an overview of all modules, scenarios and webhooks. Raynet and Pipedrive have since received a direct integration.

What Make is and how it works with Quanda

Make is an online automation platform that connects apps without code. Until 2022 it was called Integromat. You build the workflow between apps like a chain of building blocks on a canvas.

A scenario in Make is one such automated workflow. It starts with a trigger, which is an event in one of your apps (a new lead, a paid order, a closed ticket), and continues with modules that do something with the data. A module is a single step of the scenario, for example "create a contact in Quanda" or "add a row to a spreadsheet".

Quanda has its own app in Make, which according to its label in Make is developed and managed directly by Quanda. You will find the list of modules and the apps you can connect it with on the Quanda page in Make.

Make pays off wherever you move data between apps by hand today: copying emails from orders, exporting spreadsheets or adding tags after every meeting. A scenario does it for you every time, right away.

Quanda modules in Make

The Quanda app has 12 modules in Make. The names are in English in Make, so the cards below list them exactly as you will see them there.

Source: Quanda app page in Make, as of 13 October 2026.

In Quanda, tags are the bridge between Make and automations. Make adds a tag to a contact and the tag starts whatever should follow in Quanda: a welcome email, an email series or a notification for a salesperson. How to set up the follow up automations is described in the article Email automation: 8 scenarios that work for you.

How to connect Quanda with Make

You need a Make account and access to Settings in Quanda. We will show the steps on the most common scenario, where another app creates contacts in Quanda.

1. Create an API key in Quanda

In Quanda, open Settings, the API keys section, and click Create a new API key. Give the key a name, for example "Make", and save it. The steps are also described in the help article API documentation and API key. Treat the key like a password.

2. Create a new scenario in Make

In Make, click Create a new scenario and choose the app that should start the scenario as the first module. It can be Facebook Lead Ads, Shopify, Stripe, FAPI, Zendesk, Google Calendar or Google Sheets.

3. Add the Quanda module

After the trigger, add a Quanda module, for example Create or update a contact, and the first time you use it, create a connection with the API key from Quanda. Make remembers the connection and in other scenarios you simply select it.

4. Map the fields

Drag values from the trigger into the fields of the Quanda module: email, first name, last name and the tag you will then use to start an automation in Quanda. The email is required, fill in the other fields depending on what you will personalize in your emails. The Overwrite options decide whether the module overwrites saved data. For tags this means they are either replaced with the new ones or the new ones are only added to the existing ones. The module can also set GDPR details: the purpose of processing, the email sending status, the validity date and the legal basis. If you fill them in, all four must be filled in.

5. Test the scenario

Click Run once, trigger the event in the source app and check in Quanda that the contact arrived with the right tag. For each module, Make shows what data it received and what it sent, so you will find any error quickly.

6. Turn on scheduling

Save the scenario and turn it on so that it runs on its own according to the scheduling settings. Instant triggers (webhooks) run right after the event, the others check the source app at the set interval.

Tip: Before you switch the scenario on for real, set up an automation on the tag in Quanda and send the whole chain to your own email. That way you check not only the data transfer but also the email the contact will receive.

6 scenarios that save manual work

Six scenarios save the most manual work: a welcome email for a lead from an ad, an email series after a paid order, a satisfaction survey after a closed support ticket, materials after a booked meeting, a regular spreadsheet transfer and a weekly overview of sent campaigns. You can adopt each of them and adjust it to the apps you use.

A new lead from an ad gets a welcome email

The Facebook Lead Ads trigger passes on the form completed in the ad, the Create or update a contact module creates a contact with the tag "Ad lead" and an automation in Quanda sends a welcome email or an e-book. The lead gets a reply within minutes, not on Monday after an export.

A paid order starts an email series

When a customer pays via FAPI, Shopify or Stripe, Make transfers them to Quanda with a product tag. The tag adds them to an email series, for example with an online course, a product guide or onboarding.

A closed support ticket opens a satisfaction survey

When you close a ticket in Zendesk, Make creates or finds the contact and uses the Send a transactional email module to send them an email with a link to a survey. You will find a ready made template in the library as the Customer service satisfaction survey.

A new calendar meeting sends the materials

After a meeting is saved in Google Calendar, Make transfers the attendee to Quanda and sends them a transactional email with materials, a meeting link or a survey before the consultation. A transactional email is an email that Quanda sends to a single contact based on an event, not to the whole database. You prepare and activate it in Quanda following the help article Transactional emails.

A spreadsheet is transferred to Quanda regularly

If you collect contacts in Google Sheets or Airtable, the Bulk import contacts and companies (advanced) module transfers them to Quanda all at once, including companies. The scenario can run every night, for example, so you always have an up to date list in Quanda without a manual import.

An overview of sent campaigns goes to the team

The List sent campaigns search module returns the campaigns sent since a chosen date. Make can write them to a spreadsheet every Monday or post them to Slack, so the whole team knows what went out.

From practice: We have built more than 60 scenarios in Make for 26 customers. Some of them run more than 20 active scenarios and the most complex scenario has over 80 steps. It always starts with one simple scenario, though, such as transferring contacts from a CRM. At Performia spol. s r.o., for example, a scenario with more than 80 steps connects Zoom webinars, the survey at their end, Excel, Raynet CRM and Quanda. Processing more than 300 webinar attendees used to take two employees 2.5 days, now it runs automatically within 7 to 10 minutes after the webinar ends.

How to react to events in Quanda via webhooks

A webhook is an automatic message that Quanda sends to a given address when something happens in it. The Quanda app in Make has no triggers, so webhooks are the way to start a scenario from Quanda.

Quanda sends webhooks for these events:

• an email is sent,
• a recipient status changes,
• a link in an email is clicked,
• an email is opened,
• a contact unsubscribes,
• a completed survey is saved.

In Make, you create a Webhooks module with a custom webhook and get its address. In Quanda, open Settings, the Webhook section, click Create a new Webhook, choose the event and paste the address from Make. The settings offer a click on a link, an email open, an unsubscribe and a survey submitted and saved. Email sent and recipient status change are set up via the API, for example with the Make an API call module. Via the API, you can also limit the webhook with a filter to contacts with a specific tag. You will find the details in the API documentation.

A typical example: a customer completes a satisfaction survey with a low rating and, based on the webhook, Make creates a task in the CRM for a salesperson to get in touch.

Watch out: Quanda does not have a webhook for form submissions yet. What should happen after a form is completed is set directly in form automation.

Make, direct integration or Quanda HUB?

Choose Make for apps that Quanda has no direct integration with. For Raynet CRM, Pipedrive, Caris DMS and SOFTapp use the direct integration, for automations based on documents from ERP and DMS systems use Quanda HUB, and for custom development use the API.

Source: Quanda, as of October 2026.

Raynet CRM and Pipedrive have a two way integration with Quanda: they sync contacts and write sent campaigns back to the customer record. The steps for Raynet are described in the help article Connecting Quanda and RAYNET CRM, for Pipedrive in Connecting Quanda and Pipedrive CRM. Quanda HUB transfers data continuously, once an hour for running projects, and is available from the Professional plan for an extra fee.

What to watch out for

When you connect via Make, keep an eye on five things: the legal basis of your contacts, the difference between transactional and marketing emails, the security of your API key, credit usage in Make and tag names.

• Only contacts with a legal basis. Make speeds up the transfer but does not change the rules. Quanda is only for contacts you are allowed to email, more in the article GDPR in email marketing.
• Transactional does not mean marketing. The API can send a transactional email even to an unsubscribed contact. Use this only for truly transactional messages, such as an order confirmation, never for offers.
• Treat the API key like a password. Create a separate key for Make. When you cancel the scenario, you delete the key in Quanda and nothing else breaks.
• Credits in Make. Every step of a scenario uses credits. The free Make plan has 1,000 credits a month (as of October 2026), so for large volumes use the bulk import instead of individual contacts.
• Tags with clear names. Name them by source and purpose, for example "Make: Shopify customer". Six months from now you will still know where a contact came from.

Checklist: your Make scenario before launch

Before you turn the scenario on, go through these seven points.

• I have a separate API key for Make in Quanda.
• I only transfer contacts I am allowed to email.
• The scenario creates contacts with the Create or update a contact module, so no duplicates are created.
• Every contact gets a tag that identifies it and that an automation follows on from.
• The transactional email is prepared and activated in Quanda.
• I tested the scenario with Run once on my own email.
• I know how many Make credits the scenario uses each month.

Conclusion

Make turns Quanda into a hub where contacts flow in from all the apps you use and where the right emails are waiting for them straight away. Start with the one scenario you miss most today and add more step by step.

If you are not sure which route to choose, or you want to set up your first scenario with us, book a free consultation or write to us at support@onquanda.com.