How to Send Your Event's RSVPs, Check-ins and Photos to Other Apps
Webhooks let your event tell other apps what is happening the moment it happens. When a guest answers their RSVP, is checked in at the door, or a new photo appears in the gallery, Fotify sends a small message to an address you choose. From there it can land in your CRM, a Google Sheet, a Slack channel, an email sequence or your own server.
You can connect in two ways:
- Zapier or Make, with no code: connect with an API key and pick what should happen.
- A webhook URL of your own: Fotify posts a signed JSON message to it.
Webhooks, Zapier and Make are included from the Professional plan up and on every event that runs under an event subscription.
What Fotify Can Send
Each webhook listens to one or more of these moments:
- RSVP received: a guest answered or changed their RSVP. Includes their name, email, phone, answer, party size, comments and the answers to your custom questions.
- Guest checked in: a guest was checked in at the door, with the party and the person who arrived.
- New photo or video: something new appeared in the gallery. Photos come with a link to the image that works for 7 days. Photos waiting for approval are sent once you approve them, and photos in private albums are never sent.
- Event started: you started the event and guests can upload.
- Event ended: you ended the event, or its upload window closed.
Step 1: Connect Zapier or Make
- In the Fotify dashboard, open Account settings → Integrations.
- Type a name for the key, for example "Zapier", and click Create key.
- Copy the key right away. For your security it is shown only once.
- Open the Fotify app in Zapier or Make from these links (it isn't listed in their app directories yet) and paste the key when it asks you to connect.
- Choose a trigger, like New RSVP response or New photo or video, and pick your event from the list.
The event list shows the events you manage whose plan includes webhooks. Each Zap or scenario you turn on appears on the event's Webhooks page, marked Zapier or Make.
You can also use Zapier's Webhooks by Zapier → Catch Hook or Make's Custom webhook instead of the Fotify app: copy the address they give you and add it as a webhook URL in Step 2.
Step 2: Add a Webhook URL
- Open your event in the dashboard and scroll to the Webhooks, Zapier & Make card.
- Click Set up webhooks, then Add a webhook.
- Paste the address that should receive the messages. It must start with
https://and be reachable from the internet. - Tick what to send, add a label if you like, and click Add webhook.
- Copy the signing secret shown above the new webhook and store it with your receiver.
- Click Send test event to check that everything arrives.
Only people who can manage the event can add or change its webhooks, and each moment needs access to its data: guest moments need access to the guest list, photo moments need access to the gallery.
What a Message Looks Like
Every message is a POST with a JSON body:
{
"id": "4f1c2e9a-7b2d-4c1e-9a8f-2d3b4c5e6f70",
"type": "rsvp.responded",
"createdAt": "2026-06-01T18:24:05.000Z",
"event": { "id": "…", "name": "Ana & Leo's Wedding" },
"data": {
"rsvp": {
"firstName": "Alex",
"lastName": "Rivera",
"email": "alex@example.com",
"status": "accepted",
"confirmedGuests": 2
}
}
}
An RSVP's status is one of accepted, declined, not_answered, attended, pending_approval (waiting for your approval) or waitlisted. A guest waiting for approval or on the waitlist has confirmedGuests at 0 and the party they asked for in requestedGuests; rsvp.responded fires again when you approve or decline them.
The id stays the same when a message is sent again, so your receiver can skip duplicates. The headers name the moment (Fotify-Event) and the message (Fotify-Delivery).
Dates of the event itself, like eventDate and eventTime, are given in the venue's time zone, the way your guests see them.
Check That a Message Came from Fotify
Every message carries a Fotify-Signature header like t=1780000000,v1=5257a8…. To check it:
- Take
t(the time it was sent) and the raw request body. - Compute an HMAC-SHA256 of
t+.+ body, using your webhook's signing secret. - Compare the result with
v1, and reject messages whosetis more than 5 minutes old.
In Node.js:
const crypto = require("crypto");
function isFromFotify(rawBody, header, secret) {
const parts = Object.fromEntries(header.split(",").map((p) => p.split("=")));
const expected = crypto
.createHmac("sha256", secret)
.update(`${parts.t}.${rawBody}`)
.digest("hex");
const fresh = Math.abs(Date.now() / 1000 - Number(parts.t)) < 300;
return fresh && crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1));
}
You can show the secret again or create a new one from the webhook's card. A new secret replaces the old one at once.
Retries, the Delivery Log and Webhooks That Turn Off
- Answer with a 2xx status within 10 seconds to confirm a message.
- Failed messages are retried 8 times over about 4 hours.
- The delivery log on each webhook shows every message of the last 30 days, with its status, the response and the full body. Click Send again to resend one.
- A webhook turns itself off when its URL fails 50 times in a row, when the receiver answers
410 Gone(that is how Zapier and Make say a Zap or scenario was deleted), or when the person who added it no longer has access to the event. Its card says why. Turn it back on once the problem is fixed: you become the person it acts for.
Set Up Webhooks with an AI Assistant
If you connected an AI assistant like Claude, you can ask it to list your event's webhooks, add one, send a test or delete one. It needs the URL from you, and it shows you the signing secret once.
Frequently Asked Questions
Q: Which plan do I need? A: Webhooks, Zapier and Make are included from the Professional plan up and on every event subscription. On other plans the Webhooks card names the plan that includes them.
Q: Do I need a Zapier or Make account? A: Yes, to use Zapier or Make you need an account there. Webhooks to your own URL need nothing else.
Q: How many webhooks can an event have? A: Up to 25, counting the ones Zapier and Make create.
Q: Why didn't a photo reach my webhook? A: Photos are sent when they appear in the gallery. A photo waiting for approval is sent once you approve it, and photos in private albums are never sent.
Q: Can I use a URL on my own computer to test?
A: No. Fotify only sends to public https:// addresses. Use a tunnel service, or a request inspector, to test from your computer.
Q: What happens to my webhooks if I revoke an API key? A: Zapier and Make stop being able to create or remove subscriptions with that key. Delete the subscriptions you no longer want from the event's Webhooks page.
Was this article helpful?