Zoho CRM

On Zoho CRM's side

1. Note which data centre your Zoho account is on — it is the ending of the address you sign in at (for example .com, .in, .eu). MeetNotes needs it to reach the right API.
2. Create an OAuth client for Zoho CRM in the Zoho API console and issue a token with the scopes to read Contacts and create Notes. If your IT team manages Zoho, ask them for "an OAuth token for the CRM API with contacts read and notes create scopes".
3. On your Flows page add a destination of kind CRM, choose Zoho, pick the data centre, paste the token, and choose how to match contacts (email, phone, or either).

What to paste from your flow card

• Into MeetNotes: the OAuth token and your data centre. Stored encrypted, never shown again.

What we never ask for: Your Zoho sign-in, or scopes on modules other than Contacts and Notes.

How to test

1. Make sure one contact in Zoho has the email or phone number that will appear on a test call.
2. Click "Send test" on the destination to prove the token is accepted, then make a real call to a known contact.
3. Open the contact: the note is listed under Notes with the link back to the minutes.

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.

• 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.
• no matching contact — No contact in your CRM matched the email or phone number we had for the customer on that call. Skipped, not retried, no contact is created. Check the number format on the contact, or that the provider sends the caller's number at all.

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