Zapier

About Zapier integration

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 or survey object (see example #1)

• create a feedback ticket (see example #2)

Official Timebook listing on Zapier is avalable here.

Configuration

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

1

Go to Workspace settings, switch to the Integrations tab, and enable Zapier on the workplace level:

Zapier integration in workspace settings

2

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:

Zapier integration in user preferences

3

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

API key prompt screen in Zapier

Zap configuration

At the moment the integration does not support Timebook as a trigger source. If you're interested in such feature, please contact our team.

Example 1: Create interviews from Google Meet transcripts

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.

The following guide works just as well for surveys – just change the last action to Create survey instead of interview.

1

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

Google Drive trigger configuration

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:

Selecting folder with Google Meet recordings

2

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.

To ensure compatibility with Google Meet files, set the file type to .docx.

Files by Zapier configuration

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

Example comparison of input vs output from Zapier's Files action

3

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:

Formatter by Zapier configuration

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

Example data with removed tags

4

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.

Timebook interview creation event

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.

Interview creation configuration

Example 2: Create tickets from Customer Support tool

This use case describes how to automatically forward emails from a CS software to Timebook upon applying a specific tag to the conversation.

1

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.

Zap with Crisp and filtering actions

2

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

Timebook ticket creation action

3

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

Field mapping in Timebook ticket action