Skip to content
Supportqutee.aiOpen app

Connect Zammad, TANSS, Airtable or CRM Catch

Let qutee automatically create tickets in Zammad or TANSS, records in Airtable or leads for CRM Catch after calls, based on your triggers.

After a call, qutee can automatically create a ticket in Zammad or TANSS, create a record in Airtable or hand a lead over to CRM Catch. You connect the system once and use triggers to decide for which calls this happens.

  • You are signed in as a Company Admin.
  • Which systems you can connect depends on your plan. The app only shows the systems unlocked for your account. If it says “No ticket providers are available for your account.”, write to us at [email protected].
  • You have the login details for your system ready (overview below).
  1. Click your name to open the account menu and choose Integrations.
  2. Open the Tickets & automation tab.
  3. Click Add ticket connection.
  4. Click Connect for the system you want.
  5. Fill in the fields for your system (see the sections below).
  6. Click Save connection. The app reports “Connection created.” and shows the connection under Your ticket connections.

The system is now connected but not yet active. qutee only creates tickets once you add a trigger (see “Set triggers” below).

Field What you enter
URL The address of your Zammad, for example https://support.example.com
API token An access token from your Zammad profile
Default group (optional) The Zammad group new tickets go to
Default customer email (optional) The customer email under which tickets are created

URL and API token are required.

Field What you enter
URL The address of your TANSS installation
Username and Password A TANSS user that qutee creates tickets with. Ideally a separate user just for qutee
Ticket title template (optional) The subject of new tickets

URL, Username and Password are required.

You connect Airtable by signing in to Airtable instead of entering login details.

  1. Click Connect for Airtable.
  2. Sign in to Airtable and give qutee access to the base where records should be created.
  3. Back in qutee, the connection appears with the hint “Choose a base and map call fields before Airtable records can be created.” Click Edit on the connection.
  4. Choose the Airtable base and Airtable table.
  5. Map the call data to the columns of your table. Fields set to Do not map are skipped. At least one field must be mapped.
  6. Click Save changes.

You can map this call data: Caller number, Call timestamp (ISO), Duration (seconds), Call summary, Generated title, Agent name, Call result, Tags, Captured information and Call ID.

qutee hands leads over to CRM Catch as an XML file by email, not through an API.

Field What you enter
Recipient email The address at which CRM Catch accepts leads by email. Required
XML subject template (optional) Subject of the email
Campaign (optional), Lead type (optional) Values that should appear in the lead
Email contact in XML (optional) Contact email that appears in the lead

The XML file contains the summary, the caller’s number, the agent and the contact details from an Information capture of the call.

For every system you find Also send call notification email:

  • On: You get the notification email for the call as usual, plus the ticket.
  • Off: If a ticket was created for a call, the general notification email is skipped. Emails from an Information capture are still sent. For CRM Catch, the XML email is always sent.

A trigger decides for which calls qutee creates a ticket. Without a trigger, nothing happens.

  1. Click Manage triggers on the connection.
  2. Click Add trigger.
  3. Under When should this run?, choose one of the options:
    • Every call: after every call on all agents.
    • When a tag is set: choose the Tag. It runs when the call gets this tag.
    • When an agent action runs: choose Agent, Action type and Action. The Action type can be Information capture (runs when the agent captured the details during the call) or Forwarding (runs when the agent tried to forward the call to this destination, even if nobody answered there).
  4. Leave Priority at 0 or enter a higher number (see below).
  5. Click Save trigger. The app reports “Trigger saved.”

You can create several triggers per connection. Remove deletes a trigger.

Zammad and TANSS create at most one ticket per call, even if several triggers match. qutee decides which trigger counts, for example for the group in Zammad, like this:

  1. An agent action wins over a tag, a tag wins over Every call.
  2. On a tie, the higher Priority wins. The default is 0.

The ticket still contains all information the agent captured during the call.

qutee creates tickets after the call as soon as the summary is ready, usually within a few minutes. For forwarded calls, the ticket can be created while your colleague is still on the phone.

System What is created
Zammad A ticket with the summary and captured information
TANSS A ticket with the summary and captured information
Airtable A record in the chosen table with the mapped fields
CRM Catch An email with an XML file to the Recipient email
  • Edit: Change login details and options, then Save changes. If you leave API token or Password empty, the saved value is kept.
  • Reconnect (Airtable only): Renew the Airtable sign-in.
  • Delete: Removes the connection together with its triggers. Tickets already created stay in your system.
  1. Create a trigger that is sure to match, for example Every call or a tag that your test call gets.
  2. Call your agent and wait a few minutes after hanging up.
  3. Check in your system whether the ticket, the record or the email has arrived.
  4. Under Calls, the call’s details show the created tickets with their ticket ID.

Remove the test trigger afterwards if it shouldn’t apply permanently.

No ticket is created: Check whether a trigger exists and matches the call. For a tag, the call must have received this tag. For an Information capture, the agent must have filled it in during the call. For a Forwarding, the agent must have forwarded the call to this destination.

The connection can’t be saved: Check the URL and login details. For Zammad, the token needs permission to create tickets.

Airtable doesn’t create records: Base, table and at least one mapped field must be saved.

Was this page helpful?