Quanda

Quanda is a Czech B2B marketing automation platform that combines surveys, quizzes, web forms and email marketing. Agents manage contacts and tags, build and send email campaigns, send transactional email and survey invitations, read survey structures and responses, and react through webhooks.

2 triggers 38 actions API key available

Quanda website Platform Documentation Capability data verified 2026-08-26

On Survey Response fires when a completed questionnaire is saved

Get Survey Response returns every answer already resolved to readable text

Agent reads the satisfaction or NPS answer and classifies the response

Create Or Update Contact records the outcome and the purpose of processing it came with

Agent posts detractor responses to the account owner with the answers quoted

The account owner decides whether this becomes a call, a credit, or a note on the record

What This Integration Enables

Quanda is a Czech B2B platform that puts surveys, quizzes, web forms and email marketing behind one account, and the reason those belong together is more than convenience. Asking somebody a question is frequently the moment you also acquire the right to contact them, and Quanda models that literally. A contact record carries every purpose of processing attached to it, each with its own sending status, validity date and legal bases, and it is the sending status rather than any list membership that decides whether a campaign may reach that person. The record also carries the Czech vocative forms of the name, which is the kind of detail that separates a platform built for a market from one translated into it.

FlowRunner agents work across the whole surface: upserting contacts and their consent records, importing up to a thousand at a time with per record outcome counters so a partially rejected file is visible rather than silently truncated, building and sending simple campaigns from saved templates or your own HTML, dispatching transactional mail and survey invitations to a named contact, and reading survey structure and responses down to individual answers. Two triggers make it reactive as well: one fires when a response is saved, and one fires on email events. The human-in-the-loop moments on a platform like this are almost always about consent, and Quanda's API makes them unusually easy to find.

Without FlowRunner

Survey answers sit in a dashboard Responses land in a reporting screen that somebody remembers to open on a Monday

Consent is a checkbox somewhere The reason you are allowed to mail a person lives in a spreadsheet nobody maintains

Invitations ask what you already know Respondents retype the order number and the product they just bought

With FlowRunner

Answers move the moment they are saved A completed response reaches the CRM, the helpdesk or the warehouse as an event, not a report

Consent travels with the contact Purpose of processing, sending status, validity date and legal basis are read and written as record fields

Invitations arrive pre-filled Order, product and account context are prefilled and locked, so the respondent answers only what is unknown

Use Case Scenarios

A detractor reaches a person before they reach a review site

On Survey Response fires the moment a completed questionnaire is saved. The agent calls Get Survey Response, which returns each answer already resolved to readable text with its question title, so no mapping table is required. It reads the NPS or satisfaction question, and anything at the low end is routed immediately: a ticket opens in Zendesk with the verbatim comments attached, and the account owner is paged in Slack with the survey name and the answers quoted. Promoters take a quieter path, tagged for a later referral ask. The response was in somebody's hands within a minute of being submitted rather than at the end of the reporting cycle.
An invitation that already knows the context

A completed order in the ecommerce system triggers a follow up. Rather than sending a generic questionnaire, the agent reads Get Survey Structure to learn the question, subquestion and option identifiers, then calls Send Survey Invitation with the order number, the product and the delivery date already filled in. Prefilled answers cannot be changed by the respondent, and anything left out stays open, so the survey carries context without asking for it and the answers come back joined to the order. Find Contact By Email resolves the recipient first, because Quanda addresses transactional recipients by numeric identifier rather than by address.
A campaign built, proofed and sent from a flow

The agent calls Create Simple Campaign from a saved Quanda template, filling the template placeholders, then Add Campaign Recipients with the contact tags that define the audience. Addresses that are unknown, unsubscribed, invalid, blacklisted or not subscribed to the campaign's content category are skipped by Quanda and returned in a not-found list, which the agent posts as part of its proof rather than discarding. Send Test Emails goes to three internal addresses and runs the same content and spam checks a real send does, so a disallowed word or domain surfaces before anyone outside sees it. Only then is Send Campaign called. The engagement data comes back through Get Email Statistics and lands in Google Sheets for the weekly review.

Human-in-Loop Highlight

Delete Contact in Quanda is not a tidy-up. It permanently removes the contact and every record attached to it, including that person's unsubscribe status and their place in every campaign's recipient statistics. The consequence is the part worth stopping for: because the unsubscribe record goes with the contact, a person you delete today and who arrives in tomorrow's CRM sync is mailable again, and nothing in Quanda will remember that they once said no. Quanda takes the risk seriously enough that the route is disabled by default and an account has to ask support to enable it at all. So the agent treats an erasure request as a decision, not a task. It gathers what it can: whether the contact carries a recorded unsubscribe, which purposes of processing are attached and when they expire, and whether the address appears in any upstream system that syncs into Quanda. Then it asks: "Erasure requested for jan.novak@example.cz. This contact has a recorded unsubscribe from March and is present in the CRM export that runs nightly. Deleting removes the unsubscribe record with them. Delete and suppress the address upstream, or record an unsubscribe here instead?" One of those answers honors the request. The other one honors it today and quietly undoes it next week, and only a person should be allowed to pick.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

38 actions

Connection and Users

Test Connection Calls Quanda's own ping route to confirm the configured key is valid and the account reachable. Useful as the first step of a flow about to run a long import, and the quickest way to tell a rejected key apart from a plan restriction, because the two answer with different bodies.
List Users Retrieves the users of the account with their email addresses and whether each has been verified. These identifiers are what the campaign manager and collaborator fields expect, and only a verified address can be used as a campaign sender.

Contacts

List Contacts Retrieves contacts as a paginated list of identifiers and addresses, optionally narrowed by tag or exact address. Tag names are case and diacritic sensitive, and a matching option decides whether several tags mean the intersection or the union. The list carries only the identifier and the address by design.
Find Contact By Email Looks up a single contact by exact address and returns the matching identifier, or reports not found. This is the lookup the rest of the API depends on, because the transactional and invitation actions address a contact by numeric identifier. Quanda matches the whole address and only the main email field.
Get Contact Retrieves one contact in full: names and salutations including the Czech vocative forms, both addresses, all three email addresses, the six custom fields, the note, the tags with their contact counts, the companies, the owner, the content category subscriptions, and every purpose of processing with its sending status, validity date and legal bases. The sending status is what decides whether a campaign may reach this person.
Create Or Update Contact Creates a contact or updates the existing one with the same address, in a single upsert. Four overwrite switches decide what an existing record keeps, and one of them replaces the whole tag set rather than adding to it. Optionally attaches a company and records a purpose of processing with its sending status, validity date and legal bases.
Import Contacts Imports up to a thousand contacts, their companies and their consent records in one synchronous call. Returns per record counters for created, updated, skipped, invalid and ignored tags, together with the list of rejected records, so a partially rejected file is visible rather than reported as a clean success.
Delete Contact Permanently deletes a contact and every record attached to it: its unsubscribe status, its place in every campaign's recipient statistics, and its survey and form responses. This cannot be undone, and because the unsubscribe record goes with it, a deleted contact re-imported later is mailable again. Quanda disables contact deletion by default.

Contact Tags

List Contact Tags Retrieves the contact tags defined in the account, each with the number of contacts carrying it. Tags are the primary way of selecting an audience.
Create Contact Tag Creates a tag so it can be referenced by identifier before any contact carries it. Names are case and diacritic sensitive, and certain prefixes are reserved by Quanda as special codes.
Get Contact Tag Retrieves one tag with its name and the number of contacts currently carrying it. A cheap audience size check before a campaign is sent to that tag.
Update Contact Tag Renames a tag. Every contact carrying it keeps it, so this renames the audience rather than moving anyone between tags. Because tag names are matched case and diacritic sensitively, renaming breaks any flow that filters on the old name.
Delete Contact Tag Deletes a tag. The contacts are not deleted, they simply stop carrying it, which changes the audience of anything selecting on it. Recreating the tag afterward produces a new identifier with no contacts attached.

Campaigns

List Campaigns Retrieves the account's email campaigns, optionally restricted to one campaign type. Each entry carries the name, a state code, the activation timestamp and the subject. A campaign is the container; the individual sends inside it are listed separately.
Create Simple Campaign Creates a simple email campaign together with its content, in one call. The content comes either from a saved template with its placeholders filled, or from your own HTML, which Quanda validates and refuses if malformed. The HTML must contain the unsubscribe link placeholder or the campaign can never be sent.
Update Campaign Content Replaces the body and subject of a simple campaign that has not been sent yet. The same HTML validation and unsubscribe link requirement apply, and a campaign that has already been sent cannot be edited.
Add Campaign Recipients Selects the recipients of a simple campaign, either from a list of addresses or from contact tags, which cannot be combined in one call. An address is silently skipped when it is unknown, unsubscribed, invalid, blacklisted, or not subscribed to the campaign's content category, and the skipped ones come back in the response.
Send Test Emails Sends a preview to at most three addresses so rendering and personalization can be checked. Quanda runs the same content and spam checks it runs on a real send and reports the disallowed words, phrases, domains or URLs that failed. Recipients must already be selected.
Send Campaign Sends a simple campaign whose content and recipients are already in place, immediately or at a scheduled moment. A campaign that has already been sent cannot be edited or sent again.
Send Campaign In One Step Selects the recipients of a prepared campaign and sends it in a single call. Recipients resolve exactly as they do when added separately, and the content and spam checks still run, but no test email is sent first, so verify with Send Test Emails beforehand.

Sent Email and Reporting

List Sent Emails Retrieves the individual emails Quanda has sent, across every campaign type, with the campaign name, email name and subject. Filter by a sent-after timestamp to pick up everything dispatched since the last run. Each send has its own identifier, which the statistics and recipient actions take.
Get Email Statistics Retrieves the delivery and engagement statistics of one sent email: sent, delivered and not delivered counts, unique and total opens, contacts who did not open, unique link clicks, unsubscribes, timing, and a dashboard URL. A resolved flag tells you whether Quanda considers the evaluation window closed, so a flow can wait before reporting final numbers.
Get Email Content Retrieves the stored content of a sent email: its internal name, subject and complete rendered HTML. Use it to archive what was actually sent, to feed the HTML to a review step, or to clone an email into a new campaign.
Get Email Campaign Retrieves the campaign a sent email belongs to, with its name and campaign type code. Use it to tell what kind of send an email identifier came from before deciding how to handle it.
List Email Recipients Retrieves who received one sent email, with each recipient's address, delivery status, and whether they opened, clicked or unsubscribed. For a transactional email the identifier is shared by every message it has ever sent, so narrow it to one dispatch when that is what you mean.
Get Email Recipient Retrieves the full engagement record of one recipient of one sent email: delivery status and timestamps, every individual open with its timestamp and reading client, every link click with the link's URL, text and position, the unsubscribe timestamp, the spam complaint timestamp and the bounce reason. This is the deepest per person data the API publishes.

Transactional and Invitations

Send Transactional Email Sends a prepared transactional email to one existing contact, the way an order confirmation or a password notice is sent. Template placeholders are filled from the variables you supply, and files can be attached by URL, which Quanda downloads at send time and refuses the call if one does not resolve. The contact must already exist.
Send Survey Invitation Sends a transactional email carrying a survey link to one contact, with some answers already filled in. Prefilled answers cannot be changed by the respondent and any question left out stays open, which is how a survey carries order, product or account context without asking for it again. The identifiers come from the survey structure.

Surveys

List Surveys Retrieves the surveys, quizzes and questionnaires of the account. The list route returns identifiers only, so read each one for its name.
Get Survey Retrieves one survey by identifier with its name. Use it to resolve bare identifiers, or to label a survey response inside a flow.
Get Survey Structure Retrieves the complete question structure of a survey: every question with its identifier, type code, text and answer options, and for multi row questions its subquestions. Question metadata carries the per type settings such as minimum, maximum and required sum on numeric questions. These identifiers are what a prefilled invitation needs.
List Survey Respondents Retrieves the respondent identifiers of a survey, one per saved response. A respondent identifier is not a contact identifier, and the contact behind a response is only known when the respondent was identified, so an anonymous public survey yields respondents with no contact at all.
Get Survey Response Retrieves one completed response with every answer already resolved to readable text: the question title, the chosen answer, the question type code and whether the question was answered. Table questions carry the row label from the survey designer. This is what the response trigger should call to read the answers behind a notification.

Webhooks

List Webhooks Retrieves the webhooks registered on the account, each with its target URL, event name and filters. Use it to audit what is subscribed, including the webhooks FlowRunner triggers create and remove for themselves.
Create Webhook Registers a webhook that posts to your URL when the chosen event happens. Two events accept filters and the rest ignore them. Quanda expects a success response and otherwise retries five times with a widening gap before giving up. Use this action for an endpoint outside FlowRunner, because a FlowRunner trigger manages its own webhook.
Get Webhook Retrieves one registered webhook by identifier, with its URL, event and filters. Useful for confirming a subscription is still in place before relying on it.
Update Webhook Replaces the target URL, event and filters of a registered webhook. The update takes the whole record, so any filter you do not send is cleared rather than kept. Read the current state first when only one field is meant to change.
Delete Webhook Removes a registered webhook so Quanda stops posting that event. This cannot be undone, and deleting a webhook a FlowRunner trigger created will silence that trigger until it is reconnected.

Triggers

2 triggers

Event Triggers

On Survey Response Fires when a completed Quanda survey, quiz or questionnaire is saved, optionally for one survey only. The delivery carries the survey identifier and name, the respondent identifier and the timestamp. Follow it with Get Survey Response to read the answers themselves.
On Email Event Fires when a Quanda email is dispatched, opened, clicked, unsubscribed from, or when a recipient's delivery status changes. The dispatch event can be narrowed to sends touching a given contact tag and the status change event to one campaign type; the other events accept no filter. Choosing all email events subscribes to all five.

Frequently Asked Questions

What can FlowRunner do with Quanda?

FlowRunner agents can run Test Connection, List Users, and List Contacts in Quanda, plus 35 more actions.

Does connecting Quanda to FlowRunner require OAuth?

No. Quanda connects to FlowRunner with an API key, no OAuth flow required.

Can Quanda trigger a FlowRunner workflow automatically?

Yes. Quanda supports 2 triggers that can start a FlowRunner workflow automatically.

Start building with Quanda

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us