Connect HappyScribe
Connect HappyScribe with an API key so Gurusup learns from each meeting your team records, and know what comes in, who can read it and how to fix a refused key.
Admins only. From each recording Gurusup learns what was said, what was decided and who owns the next step. It adds a webhook to your HappyScribe workspace to hear when a meeting finishes.
At a glance
| Topic | Details |
|---|---|
| Who can connect | Admins |
| What you need | An API key from an owner or admin of the HappyScribe workspace |
| What Gurusup reads | Each finished meeting: details, summary, action items and transcript |
| How changes arrive | When HappyScribe reports a meeting as finished |
| Past content | None. Earlier meetings can't be imported: HappyScribe doesn't let Gurusup list them. |
| Knowledge access | Default access, Restricted or Private. See Who can read it. |
Before you start
- Get an API key from a HappyScribe account that is an owner or admin of the workspace. A regular member's key is refused.
- Check your HappyScribe workspace has fewer than 10 webhooks. Gurusup adds one, and HappyScribe allows 10.
- The same HappyScribe workspace can be connected to several Gurusup organizations, and each one adds its own webhook, so every organization counts toward the 10 webhooks. Your organization takes one HappyScribe connection.
- Meetings are often private. Decide who should read them in Gurusup before you connect.
Connect HappyScribe
Open the HappyScribe connector
In the sidebar, open Sources, then Catalog, find HappyScribe (use Search sources if you need to) and click Connect on its row. Its page opens. Next to Organization accounts, click Connect for the organization. The dialog Connect HappyScribe for the organization opens.
Choose who can read it
In the dialog, under Who can read it, keep Default access, or choose Restricted or Private from Access mode and pick the people.
Get the API key
In the dialog, the hint under the first field reads "In HappyScribe, go to Settings → Personal → API." and Show steps adds "Copy the API key of an account that owns or administers your workspace."
Paste it
Paste the key in API key. Leave Workspace ID empty unless that account manages more than one HappyScribe workspace. The hint under it reads "Only needed when that account manages more than one HappyScribe workspace."
Choose what comes in, then connect
Under What comes into Brain, leave Without a visibility label ticked to bring in your meetings (see the next section). Click Connect. A message says HappyScribe is connected.
If the key manages more than one workspace and Workspace ID is empty, Gurusup does not guess: the error lists the workspaces with their IDs. Copy the right one into Workspace ID and click Connect again.
What Gurusup reads
The form shows where each kind of meeting ends up:
| Row | Where it goes |
|---|---|
| Shared with the workspace | Whole organization |
| Shared with participants only | Not yet |
| Private | Not yet |
| Without a visibility label (a box you can tick) | Whole organization when ticked, Off when not |
Under the list the form says: "HappyScribe doesn't label meetings yet, so today every meeting falls in the last row, private ones included." So today, ticked (the default) brings in every meeting, private ones included, and unticked brings in none. Whole organization means HappyScribe's visibility does not hold the meeting back. Who reads it in Gurusup still follows its knowledge access.
Each finished meeting becomes one document:
| Part | What Gurusup keeps |
|---|---|
| Details | Title, start and end, platform, organizer and participants |
| Summary | HappyScribe's summary, under its own headings |
| Action items | Each action item with who owns it |
| Transcript | Line by line, with the speaker's name |
What Gurusup does not read
- Meetings that finished before you connected. Earlier meetings can't be imported: HappyScribe doesn't let Gurusup list them.
- Changes to a meeting after it finished. Gurusup reads each meeting once.
How changes arrive
Each time HappyScribe finishes a meeting, it tells Gurusup through the webhook, and Gurusup reads that meeting with your key. Follow it on Follow ingestion. It uses your usage like any other source.
Who can read it
What Gurusup learns from HappyScribe is one source, and its access covers every meeting.
| Knowledge access | Who reads it in Brain |
|---|---|
| Default access | Everyone, according to what they are already allowed to see: admins every category, members and agent accounts the categories an admin granted them. |
| Restricted | Only the people you pick. Administrators are not included unless you pick them. |
| Private | Only you. Administrators are not included. |
Set it under Who can read it before you connect, and it applies before Gurusup reads anything. To change it later, open the HappyScribe page and change Access mode under Knowledge access; it saves as soon as you change it. Restricting later only covers meetings that arrive after that. See Restrict a source to specific people.
Check that it worked
Check the badge
On Sources, open the HappyScribe page. Under Organization accounts, your workspace reads Connected.
Record a meeting
Record a short meeting in HappyScribe and wait for it to finish.
Follow it
Open Ingest and pick the HappyScribe source in the filter. The meeting moves to Learned.
Reconnect
If HappyScribe stops accepting the key, for example it was deleted or its user is no longer an owner or admin, the connection shows Needs reconnect. Click Reconnect on the account's row under Organization accounts. Paste a new key (and Workspace ID only if needed) and click Reconnect. Until you do, Gurusup reads no new meetings.
You can replace a working key the same way. Gurusup keeps your saved choice and your knowledge access.
Change Without a visibility label
Click Reconnect on the account's row to see your saved choice. It says "Saved with this connection; to change it, reconnect with an API key." The box cannot be changed on an existing connection, and Reconnect keeps it. To change it, disconnect and connect HappyScribe again. The new connection makes a new HappyScribe source with the knowledge access you choose then; the old source stays disconnected with what it learned.
Disconnect
On Sources, open the HappyScribe page. Under Danger zone, open the menu on Disconnect, choose Disconnect and confirm. Gurusup removes the webhook it added (yours stay) and what it learned stays; the API key stays valid in HappyScribe, so delete it there if you no longer need it. See Remove, disconnect and what stays.
If it does not work
When you click Connect or Reconnect, a failure starts with "Could not connect HappyScribe." followed by one of these:
| Message | What to do |
|---|---|
| "Paste an API key from your HappyScribe account to connect." | Paste the key in API key. |
| "HappyScribe didn't accept this API key. Copy it again from your HappyScribe API settings and paste it here." | Copy the key again from Settings → Personal → API. |
| "This API key's user isn't an owner or admin of any HappyScribe workspace. Use a key from a workspace owner or admin." | Use the key of a workspace owner or admin. |
| "This API key's user isn't an owner or admin of that HappyScribe workspace. Use a key from a workspace owner or admin." | The Workspace ID is not one that key manages. Check it, or use another account's key. |
| "This key manages more than one HappyScribe workspace. Add the workspace ID of the one to connect:" followed by the workspaces | Copy the right ID into Workspace ID and click Connect again. |
| "(workspace) already has 10 webhooks in HappyScribe, the most it allows. Remove one under Settings, Webhooks in HappyScribe, then connect again." | Remove a webhook you no longer use, then connect again. |
| "(workspace) can't send finished meetings from HappyScribe yet. Ask HappyScribe support to turn on meeting webhooks, then connect again." | Ask HappyScribe support to turn on meeting webhooks. |
| "We couldn't connect HappyScribe because of a problem on our side. Nothing was connected. Try again in a few minutes, and contact support if it keeps failing." | Try again later. Contact support if it keeps happening. |
| Meetings stop arriving | What to do |
|---|---|
| The badge reads Needs reconnect | See Reconnect. |
| Without a visibility label is unticked | No meeting comes in today. See Change Without a visibility label. |
| The meeting finished before you connected | It never comes in. |
| Ingestion paused, Demo Mode, or the item Paused on Ingest | While ingestion is paused or Demo Mode is on, Gurusup ignores new meetings. See Connector troubleshooting. |
Still stuck? Contact support with the meeting's title and when it finished.