Trigger Slack, CRM, and SMS from real identity events
Connect once. Route person-level IDs — and phones — into the tools sales and marketing already live in. Built in-house so destinations ship as templates, not another middleware project.
Ops layer for the identify → activate loop
Connect once
OAuth, API key, or webhook — then reuse the connection across templates without rebuilding every flow.
ICP-aware routing
Person-level ID plus the filters you already trust — so Slack and CRM only fire on people worth a ping.
Phone-aware triggers
On phone revealed unlocks Twilio SMS and any stack step that should wait until you have a number.
Two triggers that matter
On visitor identified
Push name, email, title, and company into HubSpot, Salesforce, Slack, Sheets, Klaviyo, and more the moment Bullseye IDs someone on your site.
On phone revealed
Fire Twilio SMS (and any follow-up that needs a number) only after a successful phone unlock — so outreach waits for a dialable contact.
Template gallery
Start from a destination, not a blank canvas. Request an integration from inside the product when you need something new.
Slack
On visitor identifiedNotify the right channel instantly
Microsoft Teams
On visitor identifiedWebhook notify your team
HubSpot
On visitor identifiedCreate contacts via OAuth
Salesforce
On visitor identifiedCreate leads via OAuth
Close
On visitor identifiedCreate leads via API key
Klaviyo
On visitor identifiedSync profiles for nurture
Google Sheets
On visitor identifiedAppend rows via OAuth
Airtable
On visitor identifiedAdd rows via API key
SMTP
On visitor identifiedSend email from your server
Twilio
On phone revealedSMS the moment a phone unlocks
Zapier
On visitor identifiedForward to a catch hook
Webhooks
On visitor identifiedPOST to any HTTPS endpoint
Coming soon: Pipedrive, Mailchimp.
FAQs
- What triggers do Automations support?
- Core triggers include On visitor identified and On phone revealed. Use the first for CRM, Slack, Sheets, and email routing; use phone revealed for Twilio SMS and any follow-up that needs a dialable number.
- Do I still need Zapier?
- Usually not for the destinations Bullseye ships natively. Zapier and custom webhooks remain available as escape hatches when you need a tool we haven’t templated yet.
- Which destinations are live today?
- Live templates include Slack, Microsoft Teams, HubSpot, Salesforce, Close, Klaviyo, Google Sheets, Airtable, SMTP email, Twilio, Zapier, and Webhooks. Pipedrive and Mailchimp templates are coming soon.
- How is this different from legacy Workflows?
- Native Automations are first-party: connect once, pick a template, and route IDs (and phones) with the filters you already use. Destinations ship in-product faster than waiting on a third-party automation layer.
- No Zapier required for core destinations
- Built for person-level events, not company IP blobs
- Request new integrations from the product
Ship identity into your stack without the glue work
Pick a template, connect the destination, and let visitor ID and phone reveal events do the routing.