Connecting other tools

The Integrations page connects Mint to the other tools you use. Open it from Integrations in the Workspace section of the sidebar.

You only see the page if you can manage integrations and API keys. In the default roles, that’s Admin and Integrations Specialist. See Team and roles.

The page has these tabs (you can ignore API keys):

Tab	What it’s for
Connections	Connect, edit, pause and disconnect integrations
Activity log	See everything your integrations have done, and any errors

What you can connect

Under Available, each integration has a Connect button:

Integration	What it does
Slack	Posts a message to a Slack channel when something happens, such as a registration, a check-in or a ticket sale
HubSpot	Keeps your HubSpot contacts in step with your Mint contacts, imports HubSpot lists and syncs unsubscribes both ways. See Connecting HubSpot
Webhook / HTTP request	Sends the details of each activity, as signed JSON, to any web address you choose
Zapier	Starts a Zap when something happens in Mint
Stripe	Not used for now: payments are being rebuilt. See Stripe payments

For other platforms, such as Salesforce, Marketo or Zoom, use the Webhook / HTTP request connection or Zapier.

Connect Slack, Zapier or a webhook

Select Connect

On the Connections tab, find the integration under Available and select Connect.
Name the connection

Name starts as the integration’s name. Change it if you’ll have more than one, for example “Slack: sales team”.
Enter the connection details

See the details each integration needs, below.
Choose when to send

Under Send when…, tick each activity that should trigger the integration. New connections start with Guest registered and Guest checked in ticked.
Save

Select Save. The connection now appears under Connected, with the status Active.

Slack

Field	Where to find it
Incoming webhook URL	In Slack, add an incoming webhook to the channel you want to post to. Slack gives you a web address starting `https://hooks.slack.com/services/`

Each message starts with a sentence saying what happened, for example “Joe Bloggs has cancelled their registration for Summer Party”. Underneath, it shows whichever of these apply:

the guest’s email, company and job title
their status, and what it was before if it changed, for example Attending → Cancelled
the order total, for ticket sales
when the event starts
how many people are attending, out of the event’s capacity if it has one, and how many are on the waitlist
the guest’s tags

Each message ends with links to Open event in Mint and View guest, which opens that guest’s details on the event’s Guests page.

Zapier

Field	Where to find it
Zapier catch hook URL	In Zapier, start a Zap with the Webhooks by Zapier “Catch Hook” trigger. Zapier gives you a web address starting `https://hooks.zapier.com/hooks/catch/`

Your Zap receives the same details as a webhook (below).

Webhook / HTTP request

Field	What to enter
Endpoint URL	The web address that should receive the details
Signing secret	A secret you share with whoever runs the endpoint. Each request then carries an `X-Signature` header (an HMAC-SHA256 of the request), so the endpoint can check it really came from Mint
Custom body (optional)	Leave blank to send Mint’s standard details (below). Or write your own body using tags such as `{{guest.email}}`
Status mapping	Optional. The value to send for each guest status, for example your CRM’s campaign member statuses. Leave a box blank to send Mint’s own status

The standard details include which activity happened and when, the event (title, dates and type), the guest (name, email, company, job title, status, check-in time and tags) and the mapped status.

In a custom body you can use these tags: {{guest.email}}, {{guest.first_name}}, {{guest.last_name}}, {{guest.company}}, {{event.title}}, {{trigger}} (the activity) and {{crm_status}} (the mapped status).

What can trigger a connection

Activity under Send when…	When it happens
Event created	Someone creates an event
Event went live	Someone takes an event live with the Website live switch
Guest registered	A guest registers, or is given a place (for example, moved off the waitlist)
Guest status changed	A guest’s status changes to anything other than attending, for example cancelled or not attending
Guest checked in	A guest is checked in
Guest unsubscribed	A guest unsubscribes from your emails
Joined virtual venue	A guest joins an online event’s virtual venue
Left virtual venue	A guest leaves the virtual venue

Connections send in the background, so they never slow down your guests.

Test a connection

Once a Slack, Zapier or webhook connection is saved, open it from the Connected list and select Send test. Mint sends a sample for the first activity ticked under Send when…, using a test event and your own name and email. A Slack test message has no attendance numbers or links, because the test event doesn’t exist. You see Test sent — check the activity log; the result appears on the Activity log tab.

If nothing is ticked under Send when…, the test can’t run and you see Choose at least one trigger first.

Edit, pause or disconnect

Select a connection in the Connected list to open it.

To change it, edit the details and select Save. Hidden fields, such as keys, tokens, secrets and the Slack web address, show Stored encrypted. Leave blank to keep the current value. Only fill them in to replace them.
To pause it, switch the Status toggle from Enabled to Paused and select Save. In the Connected list its status changes to Disabled. A paused connection sends nothing until you switch it back on.
To disconnect it, select the bin button (Disconnect) at the end of its row in the Connected list.

Activity log

The Activity log tab lists the latest 200 things that have happened in your account: every message your connections have sent, and whether it worked, along with other activity such as data retention clean-ups. It refreshes itself every 15 seconds.

To find problems, choose Errors only at the top. Each error shows the reason, for example the reply the other system sent back.