# Zapier

## About Zapier integration

{% hint style="info" %}
This feature is available in business plans only. Please contact our support if you're interested in using it.
{% endhint %}

Zapier is a tool that allows users to connect different web applications and run tasks between them by defining triggers and actions.

As for now, the integration can perform the following actions in Timebook.

* create an [interview](/hc/get-started/discovery/interviews.md) or [survey](/hc/get-started/discovery/surveys.md) object (see [example #1](#example-1-create-interviews-from-google-meet-transcripts))
* create a [feedback](/hc/get-started/discovery/feedback.md) ticket (see [example #2](#example-2-create-tickets-from-customer-support-tool))

{% hint style="info" %}
Official Timebook listing on Zapier is avalable [here](https://zapier.com/apps/timebook/integrations).
{% endhint %}

## Configuration

First, you need to connect your Timebook and Zapier accounts.

{% stepper %}
{% step %}
Go to **Workspace settings**, switch to the **Integrations** tab, and enable Zapier on the workplace level:

<div align="left"><figure><img src="/files/aHZy0P2WLBQibCdgTRbO" alt="" width="563"><figcaption><p>Zapier integration in workspace settings</p></figcaption></figure></div>
{% endstep %}

{% step %}
Next, go to your user **Preferences**, switch to the integrations tab, and flip the Zapier switch. The action will generate an API key required by Zapier:

<div align="left"><figure><img src="/files/ru3xPYnsHSON8eJSskkx" alt="" width="563"><figcaption><p>Zapier integration in user preferences</p></figcaption></figure></div>
{% endstep %}

{% step %}
Now, go to Zapier, add Timebook as a step, and paste the API key from the previous step once prompted:

<div align="left"><figure><img src="/files/xTIxbVJn7fjTSm75hxUi" alt="" width="375"><figcaption><p>API key prompt screen in Zapier</p></figcaption></figure></div>
{% endstep %}
{% endstepper %}

## Zap configuration

{% hint style="warning" %}
At the moment the integration does not support Timebook as a trigger source. If you're interested in such feature, please contact our team.
{% endhint %}

### Example 1: Create interviews from Google Meet transcripts

{% hint style="success" %}
In this example we shall create a zap which creates an interview object in Timebook whenever a new transcript file is uploaded to the selected Google Drive folder.
{% endhint %}

{% hint style="info" %}
The following guide works just as well for surveys – just change the last action to **Create survey** instead of interview.
{% endhint %}

{% stepper %}
{% step %}
Add the first step to define the trigger action. Select **Google Drive** as the triggering app, and **New File in Folder** as the event:

<div align="left"><figure><img src="/files/wcrpXCazcwCMQEcKEMwF" alt="" width="563"><figcaption><p>Google Drive trigger configuration</p></figcaption></figure></div>

The 'Configure' tab in the trigger actions lets you select the actual drive and folder to track. In this example, we narrow it down the `Meet Recordings` folder where the transcripts are stored:

<div align="left"><figure><img src="/files/mhwq2lUQJpbfPQm2Hrde" alt="" width="563"><figcaption><p>Selecting folder with Google Meet recordings</p></figcaption></figure></div>
{% endstep %}

{% step %}
Once we know which files to pick and when, we need to transform the formatted data into plaintext that can be digested by Timebook.

For this we'll use Zapier's own **Files** action with the event **Text From File**.

{% hint style="warning" %}
To ensure compatibility with Google Meet files, set the file type to `.docx`.
{% endhint %}

<div align="left"><figure><img src="/files/OVkjg2HybE2BHGQvTrB0" alt="" width="563"><figcaption><p>Files by Zapier configuration</p></figcaption></figure></div>

Once tested, the action should transform the input into plaintext:

<div align="left"><figure><img src="/files/yRiqarB5rlSNPGQYvFiy" alt="" width="563"><figcaption><p>Example comparison of input vs output from Zapier's Files action</p></figcaption></figure></div>
{% endstep %}

{% step %}
The last step before sending to Timebook is cleaning unnecessary HTML tags using Zapier's **Formatter** action.

Set the action event to **Text** and configure the 'Input' field to inject the text from the previous step:

<div align="left"><figure><img src="/files/bizX9Tc66dKg30ncHL0G" alt="" width="563"><figcaption><p>Formatter by Zapier configuration</p></figcaption></figure></div>

The result is text in clear form with minimum to no impact on further AI processing:

<div align="left"><figure><img src="/files/EwFfVO07nwwqikRcizqk" alt="" width="228"><figcaption><p>Example data with removed tags</p></figcaption></figure></div>
{% endstep %}

{% step %}
Finally, we can add the step that creates the interview object in Timebook. For this, look up the **Timebook** app and set the action event to **Create interview**.

<div align="left"><figure><img src="/files/1F3uD5KSXrIJ76dgJJtl" alt="" width="563"><figcaption><p>Timebook interview creation event</p></figcaption></figure></div>

The configuration tab has three inputs which are mirrored in Timebook.

* **Transcript**: the actual transcript in the Recoding tab. Map the field to **Step 3** → **Output** to fetch the output of the previous formatting action.
* **Product**: the product in Timebook to which the interview will be assigned.
* **Contact email**: the email of the interview participant.

<div align="left"><figure><img src="/files/ob5EMbWdi7ORUUAOzqpa" alt="" width="563"><figcaption><p>Interview creation configuration</p></figcaption></figure></div>
{% endstep %}
{% endstepper %}

### Example 2: Create tickets from Customer Support tool

{% hint style="success" %}
This use case describes how to automatically forward emails from a CS software to Timebook upon applying a specific tag to the conversation.
{% endhint %}

{% stepper %}
{% step %}
Add the first step to define the trigger action. Here we use **Crisp** as the source app, and updating conversation segment (tag) as the trigger event.

We also apply a filter which restricts the trigger segment to 'timebook'. In other words, the message will be forwarded to Timebook upon applying this tag to a user in Crisp.

<div align="left"><figure><img src="/files/r57hBSO9oCPDYQb9M8dA" alt="" width="563"><figcaption><p>Zap with Crisp and filtering actions</p></figcaption></figure></div>
{% endstep %}

{% step %}
With the trigger configured, we can now add Timebook and the action event to perform:

<div align="left"><figure><img src="/files/hrBZTNIEOaeY9hnZhbJJ" alt="" width="563"><figcaption><p>Timebook ticket creation action</p></figcaption></figure></div>
{% endstep %}

{% step %}
The last step is mapping the sources from Crisp to to Timebook. Here we populate 5 properties:

* **Title** (dynamic) – the subject of the ticket
* **Ticket description** (dynamic) – the contents of the ticket (e.g. the last message from the user)
* **Team** (static) – the team to which the ticket will be assigned
* **Contact email** (dynamic) – the email of the user whose message is forwarded
* **Severity** (static) – the priority of the ticket: `low`, `medium`, `high`, `urgent`

<div align="left"><figure><img src="/files/Fm5N8L44AXDAo8GO5GqM" alt="" width="563"><figcaption><p>Field mapping in Timebook ticket action</p></figcaption></figure></div>
{% endstep %}
{% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.timebook.ai/hc/integrations/zapier.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.