Integrations¶
An integration routes events from your groups to an external channel – such as Microsoft Teams, Slack or Zulip. This means that whatever happens in Rhizome ends up in a channel that your team is already monitoring.
Integrations can be set up by group and workspace managers.
Create a webhook¶
You need a name, an HTTPS address, a format and a selection of event types.
The available formats are Teams, Slack, Zulip and JSON. The first three generate messages that look good within their respective services; JSON is intended for your own endpoints. The language of the messages can be configured for each integration – so a channel can be in English whilst the interface remains in German.
An integration can be Active, Off or Automatically paused. The latter applies if the destination channel has repeatedly been unreachable.
Which groups to deliver to¶
A newly created integration does not grant any access. You authorise groups for it individually, and each authorisation is recorded with the date and the person responsible.
You can only share groups of which you yourself are a member. This also applies to workspace managers: anyone who is not a member of a group cannot share its events externally. Without this rule, an integration could be used to eavesdrop on private spaces without actually entering them.
You’ll also need the role of workspace Manager or Manager of this group.
What the receiving system sees
It receives the title and status of each topic and decision that are visible to the authorised groups – including option titles, group names, who has been added as a co-creator, and who has raised or resolved an objection or veto.
Discussion texts are never sent.
The receiving system stores this data in accordance with its own rules. Anyone with access to it can view this metadata. Before sharing, you must therefore confirm that you are authorised to share these groups’ events with this recipient.
Before you agree, Rhizome shows you a preview: the events that would most recently have been sent to this integration. This allows you to see, using real examples, what would leave the workspace.
Signature secret¶
Every delivery bears a signature calculated using a secret. Anyone who verifies it can confirm that the request really did come from Rhizome and was not altered in transit.
The secret is displayed only once. Make a note of it when you create it, or generate a new one later – although the old one will then no longer work and all checks on the recipient’s side will need to be updated.
You don’t need it for Slack, Teams or Zulip: these services don’t check the signature – there’s no field for it there. It becomes relevant when the integration points to a custom endpoint.
What has arrived¶
Under Most Recently Delivered Events, you can see, for each delivery, the event, the status, the number of attempts, the last attempt and the response code from the destination system.
The status is Pending, Delivered, Being retried or Failed. If something fails, it is almost always down to the destination – an incorrect address, an expired channel, or a service that is currently unavailable.