How to create an integration
- Go to the workspace you want to add an integration for
- From Workspace menu, select the workspace from the navigator
- Go to the Integrations tab.
- Select the Manage from the navigation menu and the Integrations

- Click on New Integration from the top right corner
- Select your integration type. The following types are available:

- Fill in the details for your integration. In the screenshot below, you see an example for n8n. Common to all integration setups is the option to share the instance with the rest of your organisation.

- Before adding the integration, you can test the settings via Test Connection
- Click on Add Integration to add your integration
- Integrations should have unique name per type.
- When testing an integration, the backend will give up testing after 5 seconds of trying to connect to the integration instance
- Depending on the integration type, you might see different options for the integration
How to update an integration
- Go to the Integrations tab of the workspace.
- Edit the integration.
- Select the Edit icon next to the integration you want to edit.

- Edit the integration details.
- Provide a new name for the integration (optional).
- Modify the URL of the integration endpoint (optional).
- Test the integration (optional).
- Click the Test Connection button.
- If the integration is valid, a message will appear that the integration is tested successfully. Differently, a message containing the test error will appear.
- Update the integration.
- Click the Update Integration button.
- The list of integrations will be updated automatically to reflect the new changes.
How to delete an integration
- Go to the Integrations tab of the workspace.
- Delete the integration.
- Select the Delete icon next to the integration you want to delete.
- Confirm the deletion by clicking the Delete button on the confirmation dialog that appears.
- The list of integrations will be updated automatically to reflect the new changes.

Egress control
Several integrations require Cymph to make outbound connections to an endpoint you operate — SIEM APIs (Wazuh, Microsoft Sentinel), SOAR platforms, ticketing systems, and similar. When that endpoint sits behind a firewall or a source-IP allowlist (standard practice in financial and government environments), the connection is refused unless Cymph’s egress address is permitted. Symptoms of a missing allowlist entry:- Test Connection fails with
403or a connection timeout. - A previously working integration goes dead while its status still shows Enabled — the only clue is the
403s in your own endpoint’s access logs.
The addresses to allowlist, and the notice policy for changing them, are in Networking — that is the page to hand to a network or firewall team.

