Automating with Webhooks and Event Subscriptions

StretchMeet can notify other systems the moment things happen in a meeting — a room is created, a participant asks to join, a meeting starts or ends. You do this with webhook subscriptions: StretchMeet sends an HTTPS request to a URL you choose whenever a matching event fires. This article explains how to set them up and use them.

What webhooks are for

Use webhooks to automate work around meetings, for example:

• Post a message to a team channel when a meeting is created.
• Kick off a workflow when a participant requests to join.
• Sync meeting lifecycle events to an external calendar or CRM.
• Trigger a follow-up task when a meeting ends.

Event types

You subscribe to one or more event types. Events use dotted names, and you can use wildcards to match a family of events:

• meeting.created — a new meeting room was created.
• participant.join_requested — someone requested to join a meeting.
• meeting.* — every meeting event (the default).
• participant.* — every participant event.
• * — all events.

Create a subscription

1. Open StretchMeet's Webhooks / Subscriptions area.
2. Click New subscription.
3. Enter the target URL — the HTTPS endpoint that will receive events. It must start with https://.
4. Choose the event types to subscribe to (for example, meeting.*).
5. Optionally provide a secret token (16-256 characters). StretchMeet uses it to sign deliveries so your endpoint can verify the request genuinely came from StretchMeet.
6. Set the status to active.
7. Save.

Verify deliveries

StretchMeet records each delivery attempt so you can confirm your endpoint is receiving events:

1. Open Deliveries in the Webhooks area.
2. Review recent deliveries and their outcomes.
3. If deliveries are failing, check that your endpoint is reachable, returns a success response quickly, and is validating the signature correctly.

Manage and remove subscriptions

• Set a subscription to disabled to pause it without deleting it.
• Delete a subscription when you no longer need it.

A realistic example

An operations team wants a Slack ping whenever a client meeting is scheduled. They stand up an HTTPS endpoint that posts to Slack, then create a StretchMeet subscription with target URL https://hooks.example.com/stretchmeet, event type meeting.created, and a secret token. Their endpoint verifies the signature using that token and, for each event, posts "New meeting scheduled: {title}" to the team channel. They watch the Deliveries list to confirm events are arriving, then leave it running.

Tips

• Always use HTTPS. StretchMeet requires secure endpoints — plain http:// URLs are rejected.
• Set a secret token and verify it. Signature verification is your defense against spoofed requests.
• Subscribe narrowly. Listen only for the events you act on (e.g. meeting.created) rather than *, to reduce noise.
• Respond fast. Acknowledge deliveries quickly and do heavy work asynchronously so deliveries don't time out.
• Watch the Deliveries list after setup to confirm everything is flowing.

Troubleshooting

• "Webhook target_url must use https." Your endpoint URL isn't HTTPS. Use a secure URL.
• Deliveries are failing. Confirm the endpoint is publicly reachable, returns a 2xx quickly, and isn't blocking StretchMeet. Check the Deliveries list for details.
• Events aren't arriving. Verify the subscription is active (not disabled) and that its event types actually match the events you expect.
• Signature checks fail on my side. Make sure you're using the same secret token you set on the subscription.

FAQ

What format are events delivered in?
StretchMeet POSTs event data to your HTTPS endpoint, signed with your secret token when you set one.

Can I subscribe to everything at once?
Yes — use *, but narrow subscriptions are usually easier to manage.

How do I temporarily stop receiving events?
Set the subscription to disabled; re-enable it later or delete it entirely.