When someone buys a ticket to your kirtan evening, signs up for a weekend retreat, or registers for a sound healing circle, that purchase is the start of a relationship you'll want to keep after the gathering ends. BrightStar sends each buyer into the tools you already use — your own Mailchimp, Klaviyo, HubSpot or Salesforce account, on your own key — and can tell your team in Slack as tickets sell. Once it's connected, it runs in the background instead of you copying names into a spreadsheet after every event.
Which tools does BrightStar connect to natively?
Mailchimp: sign in with Mailchimp, choose an audience, and each buyer is added with their name, the gathering, ticket type and date, and a tag for that gathering. You can also add the named attendees on each order. Klaviyo: paste a private API key and each buyer becomes a profile with a Placed Order event carrying the gathering, tickets and value, ready for your flows; buyers who agreed to marketing can also be subscribed to a list you choose. HubSpot: paste a private app token and each buyer becomes a contact, matched by email, with BrightStar properties (last gathering, ticket types, order value) and a note on their timeline; a closed-won deal per order is optional. Salesforce: sign in with Salesforce and each buyer is matched to an existing Contact or open Lead by email, or added as a new Lead (or Contact), with the purchase logged as a completed Task; existing records are never edited. Slack: paste an incoming-webhook URL and new orders post to your channel as a short summary, at most once every five minutes, along with refunds and a note when a gathering sells out or runs low. Sched and Momence connect from the same page: Sched brings your festival agenda onto your event page, and Momence brings your studio members into your BrightStar audience.
What data actually moves into your tools
Every tool receives the buyer's email, first and last name and phone, the gathering's name, date and public page, the ticket types and quantities, and the order total in its own currency. Mailchimp stores the gathering, ticket type and date in three merge fields (BSEVENT, BSTICKET, BSDATE) that BrightStar adds to your audience, plus a tag per gathering. Klaviyo receives a Placed Order event with the value, currency and one item per ticket type, identified by the order so it is never counted twice; refunds arrive as a Refunded Order event. HubSpot receives the contact's standard fields and a BrightStar property group; Salesforce receives a Task describing the purchase. Refunds reach every CRM too: a refund tag in Mailchimp, a Refunded Order event in Klaviyo, a note in HubSpot and a Task in Salesforce. Slack only ever sees a first name and last initial — never an email address or phone number.
Setting up a connection
Every tool follows the same short path:
- 1Open Dashboard → Integrations → CRM & email
- 2Choose your tool and sign in, or paste its key (each tile shows exactly where to find it)
- 3Switch on “Send new buyers” (Slack starts as soon as it's connected)
- 4Press Test connection — or Send test for Slack — to confirm BrightStar can reach your account
- 5Optionally press Sync existing buyers to bring in everyone who has already bought
- 6Watch the last 20 sync attempts under the tile
How quickly do buyers arrive?
Within seconds of a paid order in most cases, and always within five minutes: BrightStar hands each completed order to your tools as soon as payment is confirmed, and a check every five minutes catches anything that didn't go through the first time — a timeout, a busy CRM, a free ticket. Each order is delivered exactly once per tool, even when both paths see it, and a failed delivery is retried up to five times. If your key stops working, the tile turns to “Needs attention” and tells you what the tool said, and deliveries resume once you connect again.
What if my tool isn't on the list?
Zapier reaches more than 6,000 other apps with three triggers — New Ticket Buyer, New Attendee and Ticket Refunded — switched on per gathering from the Zapier tab. Behind those triggers are three read endpoints, one each for ticket buyers, attendees and refunds, returning JSON and authenticated with the API key you create on the same page. Each accepts a timestamp so you only ask for what's new since your last check, results come back in order, and every record carries its own id, so polling an overlapping window twice doesn't create duplicate contacts. Any tool that can make an authenticated request can keep itself current on its own schedule.
How does BrightStar handle data privacy and consent?
Buyer data you send to your own tools is subject to your own privacy policy, and nothing is sent until you connect a tool and switch it on. Anyone who has unsubscribed from BrightStar or been suppressed is never sent to any CRM. Consent decides subscription: in Mailchimp, a buyer who agreed to marketing is added as subscribed and everyone else as a non-marketing (transactional) contact, and because BrightStar only sets the status of new members, someone who unsubscribed in Mailchimp stays unsubscribed. In Klaviyo, only consenting buyers are subscribed to your list, and never anyone Klaviyo holds as unsubscribed or suppressed. HubSpot and Salesforce receive the contact without any change to their marketing status. Keys are encrypted at rest, and only buyers of your own gatherings on Elevate or Amplify are sent.