Integrations
Winglark talks to the tools you already use.
Your HR system, your ticket site, your CRM and your automations can hear about every reply, check-in and invitation the moment it happens — and add guests without anyone retyping a list. The API with its signed webhooks, the Zapier app, and the HubSpot sync work today. The Salesforce sync is in preparation.
- REST API and signed webhooks
- Keys shown once, scoped, revocable
- Contact details masked by default
- Your systemLive
- ZapierLive
- HubSpotLive
- SalesforceIn preparation
What people connect it for
Four jobs, in plain words.
Nobody needs an integration for its own sake. These are the four things teams ask for most often, and what each one runs on.
Our HR system should know who is coming
Each reply reaches your system as a signed webhook seconds after the guest answers: yes or no, how many, and the revised answer if they change their mind.
API & webhooksLive
Our ticket site sells, Winglark runs the door
Your site adds each buyer to the guest list through the API. A repeated request with the same idempotency key adds nobody twice, and the door knows them like any invited guest.
API & webhooksLive
We want recipes, not code
A Zapier app with triggers on Winglark’s events and actions that add or update guests, so a spreadsheet, a chat channel or a form can join in without a developer.
ZapierLive
Our sales team should see who came
Guests, their replies and their attendance written to the matching contacts in HubSpot or Salesforce, so a follow-up starts from who actually walked in.
HubSpotLiveSalesforceIn preparation
What connects
Where each one stands.
Each card says where it stands. When one opens, its card, its page and the pricing table change together.
API & webhooks
LiveFor your own systems and developers
Workspace API keys, a REST API for events, guests, replies and check-ins, and signed webhooks for thirteen events.
On Professional and Agency
Zapier
LiveFor no-code automations
Triggers on Winglark’s events, and actions that add or update guests — built on the same API and webhooks.
On Professional and Agency
HubSpot
LiveFor marketing and sales in HubSpot
Guests, replies and attendance kept on the matching HubSpot contacts.
On Professional and Agency
Read moreConnect from Integrations → CRMSalesforce
In preparationFor sales in Salesforce
Guests, replies and attendance kept on Salesforce contacts or leads.
On Professional and Agency
One message from our team when it opens, through the contact form. No mailing list.
In the product
Keys, webhooks and every delivery, on one screen.
Integrations sits in the workspace settings. A key is created with the scopes it needs and shown once; an endpoint is given the events it should hear; the delivery log shows what was sent, what came back and what is being retried.
- Scoped keysRead events, read or write guests, read replies and check-ins, manage webhooks — a key carries only what it was given.
- A log you can act onEvery delivery with its status and attempt. Send one again, or send a test event before going live.
- Failing endpoints pauseAn address that keeps failing is paused instead of retried forever, and the screen says why.
Illustrative workspace, keys and deliveries. The screens are drawn from the product as it works.
How it moves
Something happens at the event. Your system hears about it.
Winglark signs each message and sends it to the address you choose. Your system can also ask, through the API, and add guests of its own.
- A guest repliesOr is invited, checked in, given a ticket or a printed badge.
- Winglark signs and sendsA JSON message with a timestamped signature, retried over 24 hours if your side is down.
- Your system actsIt updates the record, tells the team or asks the API for more.
POST /winglark HTTP/1.1
Winglark-Signature: t=1762338012,v1=5f2b…c9e1
Winglark-Event: rsvp.submitted
Winglark-Delivery: 7c1e9a42-…
{
"type": "rsvp.submitted",
"created_at": "2026-11-05T18:40:12.481Z",
"event_id": "6f1c2a7e-…",
"data": {
"response": "yes",
"party_size": 2,
"guest": { "first_name": "Ada", "email": "a•••@example.com" }
}
}Contact details stay masked unless the endpoint is allowed to see them.
A webhook, opened
Signed, timestamped, and the same every time.
Each message carries the event type, the event it belongs to and the record that changed. The signature covers the time and the exact bytes, so a copied or replayed message is refused.
The events an endpoint can subscribe to
- guest.created
- guest.updated
- guest.archived
- rsvp.submitted
- invitation.sent
- invitation.delivered
- invitation.bounced
- checkin.admitted
- ticket.issued
- event.published
- event.cancelled
- seatmap.published
- badge.printed
Security
Built so a key can do exactly one job.
Integrations reach into the guest list, so they follow the same rules as the rest of Winglark.
- Shown once, stored as a hash
- A key is visible only at the moment it is created. Winglark keeps a keyed hash, never the key.
- Scopes and expiry
- Each key is limited to the scopes chosen for it, can expire on a date and can be revoked at any moment.
- Signed webhooks
- An HMAC over a timestamp and the body, with secret rotation that keeps the old secret valid for an overlap.
- Contacts masked
- E-mail addresses and phone numbers arrive masked unless the key or endpoint is allowed to see them.
- Stored in the EU
- Workspace and guest data stay in the European Union, as described in the Trust Center.
For developers
Every route, field and signature, written down.
The developer reference covers authentication, pagination, idempotency, errors and rate limits, every endpoint with its scope, all thirteen webhook events, and signature checks in Node and Python.
Plans
On Professional and Agency.
Workspace API keys and webhooks come with the Professional and Agency plans. Free, Starter and the Single Event do not include them. Every connection on this page is on the same two plans. The Zapier app and the HubSpot sync work today. The Salesforce sync is in preparation.
Compare the plans →Questions
Do you have an API for guest lists?
Yes. The REST API lists, reads, creates and updates guests for each event, and reads replies and check-ins. Lists are paged with a cursor, a create can be repeated safely with an idempotency key, and every key is rate limited. It is on the Professional and Agency plans.
Can Winglark send our RSVPs to HubSpot?
Yes. Connect HubSpot from Integrations → CRM in a few clicks: each guest becomes a HubSpot contact matched by e-mail address, kept up to date when they reply and when they arrive. On Professional and Agency.
How do I connect Winglark to Zapier?
Open the invite link on the Zapier page, then connect with an API key from Integrations → API keys. Recipes start from a new guest, a reply, a check-in and five more triggers, and can create or update guests. On Professional and Agency.
Does it work with Salesforce?
A Salesforce sync to contacts or leads is in preparation. The API and webhooks it will be built on work today, so a Salesforce developer can connect them now.
Which events can a webhook tell us about?
Thirteen: a guest created, updated or archived; a reply submitted; an invitation sent, delivered or bounced; a guest admitted at the door; a ticket issued; an event published or cancelled; a seating plan published; and a badge printed.
What happens if our server is down?
Winglark retries each delivery on a fixed schedule over 24 hours and records every attempt in the delivery log, where you can send it again. An endpoint that keeps failing is paused, and the screen says so.
Can an API key see our guests’ e-mail addresses?
Only if it was created to. By default e-mail addresses and phone numbers are masked in every response and webhook, and a key that may see them says so on the Integrations screen.
Connect Winglark to the rest of your day.
Start with an event, then give your systems a key when you are ready.