Exotel

On Exotel's side

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

1. In the Exotel dashboard open App Bazaar and edit the call flow (applet) that handles the line.
2. Add or open the Passthru / Status Callback step and paste the MeetNotes URL from this card as the callback URL.
3. Make sure recording is ON in the Connect/Dial applet so the callback carries RecordingUrl.
4. Save the flow. Exotel posts a form to the URL when each call ends; a call without a recording is skipped and revived when the recording arrives.
5. Recordings download without a login on most accounts; if yours needs one, set it under "If the recording needs a login".

What to paste from your flow card

• The MeetNotes URL from the source card — Exotel calls it the callback URL. It is shown once when you add the source; rotate it from the card if it leaks.
• Nothing else. Exotel posts are not signed, so there is no secret to copy the other way.

What we never ask for: Your Exotel login, your account SID or API key. We only need the callback URL to exist inside your flow.

How to test

1. Make one short real call on the line — a colleague calling in is fine.
2. Within a few minutes the recent activity on your Flows page shows the call as received, then done, and the meeting appears in the workspace.
3. If it shows skipped with recording_url required, recording is off in the Connect/Dial applet.

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.