Knowlarity

On Knowlarity's side

These are the same steps your Flows page prints on the source card.

1. In SuperReceptionist go to Settings > Integrations (or ask your account manager for the "call hangup webhook").
2. Paste the MeetNotes URL from this card as the webhook URL and choose JSON as the format.
3. Enable call recording on the number so the payload carries resource_url.
4. Save. Knowlarity posts once per finished call; a post without a recording link is skipped and revived when it arrives.

What to paste from your flow card

• The MeetNotes URL from the source card, as the webhook URL, with JSON as the format.
• Nothing else — Knowlarity posts are not signed.

What we never ask for: Your SuperReceptionist login or API key. The webhook URL is the whole connection.

How to test

1. Make one short call to the number.
2. Watch the recent activity on your Flows page: received → done, then the meeting appears.
3. If nothing arrives, check the webhook was saved on the right number and that recording is on.

When an event shows failed or skipped

The Flows page prints one short reason per event. Here is what each one on this connector means and what to do.

• fetch failed — We could not download the recording from the link the provider sent — the link had expired, it needed a login we do not hold, the file was over 300 MB, it pointed at a private address, or the server did not answer. We retry a few times before giving up. If your recordings need a login, set "If the recording needs a login" on the source.
• audio files only — The file was not audio — a picture, a document, or (except from a Drive folder) a video. Only a Drive folder source accepts video; every other door wants an audio file.
• audio unreadable — The file was named like audio but could not be decoded: empty, cut short, or not the format its name claims. Not retried. Send the recording again from the provider.
• no minutes — Your workspace had no pooled minutes left, so we did not download the recording. Skipped, not retried. Top up the pool and have the provider send the recording again.
• processing failed — The recording came in but something on our side failed after that. We are alerted automatically; if it keeps happening, write to support@getmeetnotes.com with the reference shown on the Flows page.

The full list, across every connector, is on the setup index.