Which plan includes this?

Outgoing webhooks, app events and the REST API come with Business, Corporate and Enterprise. See pricing for the plans and how many webhooks each allows.

How do I check a delivery is really from Freesbe?

Compute the HMAC-SHA256 of the timestamp, a dot and the raw body under the webhook's secret, compare it with v1 in the Freesbe-Signature header, and reject timestamps older than a few minutes. The guide has the code in Node.js.

Which channels do events come from?

Channel events come from public channels, or from the one channel you picked. The workspace's own events, like people, meetings, bookings and the punch clock, go to webhooks on All public channels. Apps hear DMs and private channels once their bot is added.

What if my server is down for an hour?

Deliveries that fail are retried 8 more times over up to 8 hours, and the webhook's Deliveries log shows each attempt for 14 days.

Business and up

Your server hears what happens, signed and retried.

An outgoing webhook sends a signed POST to your server for the events you choose, from new messages and reactions to people joining, meetings scheduled, recordings ready and someone clocking in. Apps get the same events in Slack's Events API format. Deliveries are signed, retried for hours when your server is down, and logged for 14 days.

Pick from 30 events in five groups: messages, channels, people, huddles and meetings, and the punch clock.
Check every delivery with an HMAC signature and a timestamp.
Lose nothing when your server is down: failed deliveries are retried for hours.
Reuse your Slack event handlers, with events in Slack's envelope and Slack's signature.

Start free Book a demo See pricing

For Developers wiring Freesbe into their own systems, from HR onboarding to a data warehouse.

30 events, in five groups

An admin adds an outgoing webhook with a name and a payload URL, keeps it on all public channels or picks one, and ticks the events. Messages: new, edited and deleted messages, files shared, reactions added or removed. Channels: made, renamed, new topic, archived, people joining or leaving. People: someone joining the workspace, their profile, role or status changing, being deactivated. Huddles and meetings: starting, ending, joining, scheduled, changed, canceled, a guest waiting, bookings, recordings and transcripts ready. Punch clock: in and out.

The outgoing webhook form with its events in groups

Signed, and retried until it lands

Each request carries Freesbe-Event, Freesbe-Delivery and a Freesbe-Signature header: an HMAC-SHA256 of the timestamp and the raw body under the webhook's secret, which is shown once when you create it. A delivery that fails or gets a 5xx, 408 or 429 is retried 8 more times, from 30 seconds up to 8 hours apart; any other 4xx stops it. Send test fires a webhook.test event, and Deliveries on the webhook's card shows the last 14 days of attempts.

Recent deliveries: message and reaction events, delivered

See it on your own team's data.

Start free with up to 10 people and try it today, or book a 20-minute demo with the people who make Freesbe.

Book a demo Start free

Events for your apps, in Slack's format

An app can hear what happens where its bot is: messages and reactions in its channels and DMs, mentions of the app, channel changes, people joining, huddles starting, meetings scheduled, recordings ready. Set a request URL and tick events when you edit the app, or paste a Slack manifest with event subscriptions; ticking an event ticks the scope it needs. Freesbe checks the URL with a challenge the way Slack does, and sends each event in Slack's event_callback envelope.

Signed twice: X-Slack-Signature for Slack's SDKs, and Freesbe-Signature
Answer with any 2xx within 10 seconds; failures are retried for about 13 hours
An app never hears what its own bot did, so it can't talk to itself

Editing an app: the request URL and the events it gets, each with the scope it needs

Follow everything live, DMs included

To react to messages in DMs and private channels, presence, statuses or huddles as they happen, open the workspace's WebSocket with the same bearer token. The API reference lists the frames and every event. For a Zap, a Make scenario or an n8n workflow, you don't need any of this: the automation tools connect with one key and make their own hooks.

Workspace settings, Webhooks, with incoming and outgoing webhooks

Plans and pricing

Events and outgoing webhooks is included in Business, Corporate and Enterprise.

See pricing Every plan's limits

BusinessUp to 500 people
CorporateUp to 2,500 people
EnterpriseOver 2,500 people

Questions

Which plan includes this?: Outgoing webhooks, app events and the REST API come with Business, Corporate and Enterprise. See pricing for the plans and how many webhooks each allows.
How do I check a delivery is really from Freesbe?: Compute the HMAC-SHA256 of the timestamp, a dot and the raw body under the webhook's secret, compare it with v1 in the Freesbe-Signature header, and reject timestamps older than a few minutes. The guide has the code in Node.js.
Which channels do events come from?: Channel events come from public channels, or from the one channel you picked. The workspace's own events, like people, meetings, bookings and the punch clock, go to webhooks on All public channels. Apps hear DMs and private channels once their bot is added.
What if my server is down for an hour?: Deliveries that fail are retried 8 more times over up to 8 hours, and the webhook's Deliveries log shows each attempt for 14 days.

How it works, step by step

The help guide shows every screen and setting. Outgoing webhooks

See more on this topic

Try all of it free with up to 10 people.

No card, no time limit. Invite your team and see what sticks.

Start free Book a demo