Supernormal uses a key and ID scheme for authentication with Zapier. These values can be found on the integrations page after enabling the Zapier integration option. In order to revoke credentials return to the integrations page and disable the toggle. This will remove your credentials from Supernormal. In order to use the feature once the credentials have been revoked, it is necessary to generate new credentials. In order to due so, follow the instructions for Generating API Keys again. Please note that when regenerating credentials they will be different and will require updating in the Zapier platform.
Generating API Keys
On the integrations page (https://app.supernormal.com/settings/integrations), click the toggle next to the Zapier Logo. This will generate the keys needed for Zapier to integrate with Supernormal.
Usage in Zapier UI
The easiest way to verify the credentials and integrate with Zapier is to create a new application connection. This is a one time setup and once connected, the same account can be used in any number of Zaps.
On the Zapier Dashboard, first click the “My Apps” button in the left hand navigation panel. This will load the Apps page.
On the Apps page, click the “Add connection” button and a new window will open with a search box. In this search box, type “Supernormal” and the Supernormal application will show up below the search box. Click the Supernormal logo or name and a final screen will open with a form into which the credentials should be entered.
This is the page into which the Supernormal credentials should be entered. It is easy to confuse the two credentials (Key and Key ID) and they are not interchangeable. The Key ID is the shorter of the two and goes in the bottom box. The Key is the longer value and it goes into the top box. Input the credentials and click the large orange box “Yes, Continue to Supernormal”
New Meeting Note
Each meeting in Supernormal will result in one or more “New Meeting Note” trigger events. A single meeting may have multiple types of notes and there will be one event per note type. The ‘kind’ field will specify the type of notes returned in the trigger event, such as ‘summary’ or ‘action items’. See the kind field for more details.
The example data shown here is the same example data found when setting up a new Zap if no live data is returned from the test run.
The title of the meeting which is derived from the corresponding calendar entry if possible.
ex: “Setting Up Supernormal's New Meeting Trigger” or “Meeting on July 1st, 2023 13:45”
The time that this meeting was published. This time may be slightly different than the scheduled calendar event time.
Possible Values: action-item, bookmark, decision, insight, pain-point, summary, customer-need, customer-feedback, customer-summary, customer-goals, discovery-summary, status-update-by-topic, status-update-by-person, recruiting-summary, vc-pitch-summary, give-presentation-summary, receive-presentation-summary, receive-feedback-summary, job-interview-summary, info-interview-summary, one-on-one-person1-summary, one-on-one-person2-summary, job-interview-qa
The notes of the meeting. Depending on the type of note, there can be one or many values returned. All the notes of a given kind are returned in an individual trigger event. The individual notes within each trigger event are delineated by “\n-”
ex: “- User1 to look into user login issue
User1 to document the Zapier website
User1 to work on launching features and handling edge cases
User2 to work on linking items and allowing them to be checked off
User3 to provide information for User2 in the documents
Team to work on improving system confidence and logging
User1 to look into turning on parameter logging
User1 to ensure sensitive information is removed
User3 to finish approving requests
User3 to start writing tests for the organization”
A short summary describing the meeting. This gist could be a transcript of the meeting, or the actual video recording.
ex: “Summary of the media”
A URL the user can share to provide access to the meeting, notes, and media.
Each meeting in Supernormal will usually result in one or more “New Task” trigger events. A single meeting may have multiple tasks assigned to a user and each will generate a “New Task” trigger.
The details of the task.
ex: Setup the New Task Trigger
The urgency of the task. One of “P0”, “P1”, “P2” in decreasing order or urgency.
The Meeting from which this task was derived.
ex: “Supernormal Zapier Setup”
Example Zap Setup
This section will provide the steps to setup a few example Zaps using the Supernormal integration. These Zaps are also available as Templates. A basic understanding and familiarity with Zapier and Zaps is expected. For more general information on Zaps, please consult the Zapier documentation: https://help.zapier.com/hc/en-us/articles/8496309697421-Create-Zaps#build-zaps-using-ai-beta--0-0
New Meeting to Slack
This integration will detail the steps necessary to post a message to Slack when a new Meeting occurs in Supernormal. It uses the “New Meeting Notes” Supernormal trigger and requires an account with Slack.
On the Zapier Dashboard, click the large “Create Zap” button. This will open the Zap UI window.
On the Zap UI window, click “Untitled Zap” in the top left and give the Zap a descriptive name, such as “New Meeting to Slack”
Setting Up the Trigger
The first step is to get data into the Zap. This is done by modifying the Trigger step.
In the Zap UI window, click the first of the two step boxes where it says “Untitled Step”. It is also labeled with a “Trigger” identifier. It is the top box in the following screenshot.
This will open the Change Trigger window which lists a few example integrations. In the search box, type “Supernomal” and choose the Supernormal App that shows up in the list below the search box.
Zapier will open the trigger details window asking for an App and an Event. The application will be automatically filled in with Supernormal. The event dropdown has two options: “New Meeting Notes” and “New Task”. For this example choose the “New Meeting Notes” event and press the large “Continue” button.
Next, Zapier needs to know which account to use with Supernormal. If you followed the “Usage in Zapier UI” instructions in the Authentication section above, then click the “Choose” button and the account will be listed. If not, please refer to that section before continuing.
Once you’ve chosen the account, Zapier will open the “Test” portion of the window.
Click “Test Trigger” and one of two things will happen:
No meeting notes will be found. This is normal and not indicative of an issue. This occurs when there is no meeting found in the last 24 hours. It is ok to then click “Skip test”. This will then use the default sample data for the following steps.
Meeting notes will be found. If there have been any number of recorded meetings with notes in the last 24 hours, they will be shown in the following dialog window.
Choose which meeting to use as the test data for the next steps of the zap. The dialog will be populated with either sample data or the meeting chosen in previous step.
Setting up the Action
Now that there is test data, it is time to setup the Action. This tells Zapier what to do with the information returned from the trigger.
Following from the last section, the “Change action” window should be open. If not, simply select the second step box, labeled “Untilted Step”.
In the search box, type “Slack” then choose the Slack integration that appears below the search box.
In the window on the right, App & Event, Slack is now listed. For the event, choose “Send direct message” from the dropdown and press Continue.
Choose the Slack account and press Continue.
There are multiple fields that now open for the event. For this integration we will only be modifying two. “To Username” and “Message Text”.
Press Continue which will bring up the Test portion of the action.
Click the Test button. This should generate a new message to Slack from Zapier with the test data.
The new Zap is setup and ready to run.