What has been verified
Running against the provider’s production API.
Instead of asking staff to keep a dashboard open, Boris posts the events that need a human into Slack: a new booking, a failed payment, a check-in that has not happened.
Available Running against the provider’s production API.
Running against the provider’s production API.
Requires an active provider account, credentials and any plan required by the provider.
The workflow and limitations documented on this page are the supported scope; validate it with test data before production.
The team sees the same operational events without each person interpreting the calendar differently.
Choose which events reach Slack so the channel stays useful instead of noisy.
A failed payment or a pending check-in is visible where the team is already working.
Create an incoming webhook in your Slack workspace.
Paste it into the Slack integration in Boris and pick the channel.
Select the events you want posted and confirm with a test message.
An incoming webhook is enough; Boris only posts messages and does not read your workspace.
Yes. Each workspace keeps its own Slack configuration and target channel.
Create a workspace, add your resources and connect the tools you already pay for. No credit card required.
Create your workspace