What the Toast connection does
Event Captain finds interested corporate event planners so your team can handle the conversations and close the bookings. When one of those bookings is paid through Toast, the Toast connection gives Event Captain a way to link that order back to the outreach that came before it.
The connection uses a Toast API credential set that you create in Toast Web and copy into Event Captain. It covers the Toast locations you choose.
Orders are linked using the guest’s email. That is why the credential set needs the guest.pi:read scope: without it, Toast doesn’t share the guest’s email, so no order can be linked to your outreach.
How it fits your workflow
- Event Captain reaches the people who plan events at nearby companies and follows up until they’re ready to book.
- Your team handles the conversation and closes the booking.
- When the event is paid through Toast at a location you connected, the guest’s email on the order is what lets Event Captain connect it to that outreach.
Limits to know
- Toast’s API access requires an RMS Essentials or higher subscription. If you’re not sure of your plan, check with your Toast account rep.
- The
guest.pi:readscope is required. Without the guest’s email, an order can’t be linked to your outreach. - Only the locations you choose are tracked.
- Until your first event comes through, the Integrations page in your dashboard may show that it’s still waiting for the first one. That’s expected.
How results are counted
These are Event Captain’s general attribution rules. They are not specific to Toast. For Toast, the help guide documents the guest’s email as the detail used to link an order to your outreach.
- An event counts as influenced only when your outreach reached the lead before they inquired or booked: an email you sent, a reply, a survey, a pricing request, or a call or site visit your outreach set up.
- Influenced Revenue only includes confirmed events.
- Guests who found you on their own, through search, a referral, or a walk-in, and booked without any outreach from you, aren’t counted.
The full rules are in How Event Captain calculates your metrics.
Setup summary
- In your Event Captain dashboard, open Get Started and choose the step for connecting your event software, or start from the Toast card on the Integrations page.
- In Toast Web, create a new Standard API Access credential set named Event Captain, give it the scopes
orders:read,guest.pi:readandrestaurants:read, and choose every location you want tracked. - Copy the Client ID and Client secret into Event Captain and click Connect. Event Captain checks them with Toast right away and shows your locations to pick from.
- Import your past customers, or click Skip for now.
The step-by-step instructions, with the menu names you’ll see in Toast, are in the help guide: Connecting your event software.
Questions
Which Toast plan do I need?
Toast’s API access requires an RMS Essentials or higher subscription. Your Toast account rep can confirm your plan.
Why does Event Captain ask for guest.pi:read?
Without it, Toast doesn’t share the guest’s email, so no order can be linked to your outreach.
Can I connect only some of my locations?
Yes. You choose the locations when you create the credential set in Toast, and you pick from your locations in Event Captain after connecting.
Does every Toast order count toward my results?
No. An order only counts when your outreach reached the lead before they inquired or booked. Guests who found you on their own aren’t counted.
What if I use a different system?
Toast is one of several systems listed on the Event Captain integrations page. If yours isn’t listed, choose Other in the dashboard and send a request for it.