Integrations
Connect any tool with webhooks and an open API.
Freesbe connects to other tools in three ways. Incoming webhooks post alerts, deploys and form submissions into a channel and accept Slack's JSON. Outgoing webhooks send signed events to your server. The REST API at api.freesbe.net reads and writes anything a person can, with a bearer token.
Incoming webhooks, Slack compatible
An admin creates a secret URL that posts into one channel. Any tool that can post to a Slack or Microsoft Teams webhook, such as CI, monitoring or form tools, can post to Freesbe with the new URL. Block Kit and Teams cards show as cards, with their facts and link buttons.
Outgoing webhooks, signed
Choose events like message.created, reaction.added or member.joined, and Freesbe posts them to your server with an HMAC-SHA256 signature. Failed deliveries retry 8 more times over up to 8 hours, and the last 14 days of attempts are listed.
A REST API for everything else
The API covers messages, channels and DMs, people and invites, guests, meetings, booking links, calendar free/busy, the punch clock and workspace settings. Each endpoint lists who may call it, with an example request and answer.
- JSON over HTTPS with a bearer token
- A realtime WebSocket for live events
- A separate account per integration, with its own permissions
Questions
- Do I need to change my Slack integration code?
- Not for incoming webhooks. Freesbe accepts the same JSON as Slack's incoming webhooks, so swap the URL.
- Which plans include webhooks and the API?
- The Free plan includes one incoming webhook. Business and above include unlimited incoming webhooks, outgoing webhooks and the REST API.
- How do I check a webhook really came from Freesbe?
- Each request carries a Freesbe-Signature header: an HMAC-SHA256 of the timestamp and raw body under your webhook's secret. The guide has a Node.js example.
- Where is the API documented?
- The API reference lists every endpoint, grouped like the app, with who may call it and examples.