Connect Beehiiv to send event registrations to a Beehiiv publication. You can add subscriber tags and map attendee names or registration answers to existing custom fields. HeySummit continues to send your event emails separately.
Before you start
Your HeySummit plan must include direct CRM and email integrations.
Your Beehiiv account needs API access. Create an API key that can read your publications and custom fields, create or update subscriptions, and add tags if you plan to use them. Keep the key private.
Create any custom fields you want to use in the chosen Beehiiv publication before mapping them in HeySummit. HeySummit does not create missing Beehiiv fields.
Connect your publication
In your event dashboard, open Event Settings > Integrations & Developer > Integrations.
Under CRM & Email Integrations, choose Add.
Choose Beehiiv and enter your Beehiiv API key.
Select the Beehiiv publication that should receive your attendees. A key and publication are required before you can save.
Add subscriber tags if you want to identify attendees in Beehiiv.
Map names, standard attendee fields or custom registration answers to the existing Beehiiv custom fields you want to populate.
Choose Save.
Publication and field choices load after Beehiiv accepts your key. New registrations sync after the integration is saved. To send existing registrations, open the integration's action menu and choose Resync Attendees.
Consent and subscriber status
If your event uses HeySummit's GDPR marketing opt-in checkbox, attendees who opt out of marketing emails are not synced.
Existing unsubscribed Beehiiv subscribers remain unsubscribed. Connecting or resyncing does not reactivate them.
HeySummit does not request an additional Beehiiv welcome email when creating a subscriber. Beehiiv's own subscription and double opt-in settings still apply.
HeySummit event email preferences and Beehiiv subscriptions are separate. Check that your consent and privacy policy cover the marketing you send from Beehiiv.
If the connection or sync fails
If Beehiiv rejects the key, check that you copied the current key correctly.
If access is denied or a publication is missing, check the key's permissions, the publication it can access and your Beehiiv account's API access.
If a mapped custom field is no longer available or Beehiiv cannot apply it, review the publication's fields and update your mappings before retrying.
If Beehiiv is temporarily unavailable or rate limited, try again shortly.
For the shared integration workflow and event-email behavior, see CRM & Email Integrations.