Email

On Email's side

1. On your Flows page choose "Add an email source". Copy the address the card shows.
2. Decide who may send. Your workspace members always can; add any other domain (a client, a call-recording service) under "Save senders" on the card.
3. Forward recordings to the address as attachments — a voice note, an mp3 or m4a, a wav. One attachment per email is simplest; several are each filed separately.
4. For minutes going OUT: add a destination of kind email with the addresses that should receive them, comma-separated, up to ten.

What to paste from your flow card

• The source address from the card — into whatever sends the recording: a forwarding rule, a call recorder's "email recordings to" setting, or a person's address book.
• Nothing goes into a provider console; the address is the whole connection.

What we never ask for: Access to your mailbox. We read only what is sent to the source address; we never log in to your mail.

How to test

1. Send one short audio file to the address from your own workspace email.
2. Within a few minutes the recent activity shows received → done and the meeting appears, titled with your subject line.
3. An email with no audio attachment is logged as audio files only — attach the file rather than a link to it.

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.

• sender not allowed — An email arrived from an address that is neither a member of your workspace nor on the source's allowed-domain list. Add the domain under "Save senders" on the card, or send from a workspace address.
• sender not verified — An email came from an allowed address, but the mail itself did not prove it: it failed SPF for the sender's domain and carried no DKIM signature from that domain. A From: line can be typed by anyone, so we only trust the one the mail system vouched for. Send from the domain's own mail server (Google Workspace, Microsoft 365 and the like pass this by default), not a forwarder that rewrites the message.
• 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.
• delivery failed — Your endpoint, channel or CRM did not accept the post — it was unreachable, answered with an error, or timed out. We retry, then mark the delivery failed. Use "Send test" on the destination after you have checked the URL or token.

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