HubSpot
We look the contact up by the email or phone number we have for the customer on the call (from the provider's payload, or the `customer` field you posted), then add a note to that contact: title, date, a short summary, action items, and a link to the full minutes. No contact is created and nothing else is written.
Checked 2026-08-29 · every step is done on your Flows page or inside HubSpot; nothing here needs support.
On HubSpot's side
- In HubSpot, create a private app for your account — look for Private Apps under the account's integrations settings. Give it the scopes to read contacts and to write notes (the CRM objects scopes for contacts and notes).
- Copy the private app's access token.
- On your Flows page add a destination of kind CRM, choose HubSpot, paste the token, and pick whether to match contacts by email, phone, or either.
- Optionally tick "Only send meetings with a watch-out", or limit the destination to some sources, if you do not want every call noted.
What to paste from your flow card
- Into MeetNotes: the private-app access token. It is stored encrypted and never shown again.
- Nothing goes into HubSpot from MeetNotes except the notes themselves.
What we never ask for: Your HubSpot login, a super-admin user, or scopes beyond contacts and notes. If the token is ever revoked in HubSpot, deliveries simply fail until you paste a new one.
How to test
- Make sure one contact in HubSpot has the email or phone number that will appear on a test call.
- Click "Send test" on the destination to prove the token is accepted; a real call to a known contact is the true test of matching.
- Open the contact in HubSpot: the note appears on its timeline 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.
Ready to connect it?
Open your workspace's Flows page — managers and owners see it under the team.
