The Gladius Regulatory Hub offers integration with your firm's communication environment through the use of Slack Incoming Webhooks. This feature enables the platform to push real-time notifications and “Call to Action” alerts, such as pending CASS RP approvals, upcoming third-party bank due diligence deadlines or regulatory breaches, directly into your preferred Slack team channel. By bridging the gap between your regulatory data and your primary collaboration tool, the integration ensures that critical updates are visible to the right stakeholders instantly, reducing manual oversight and optimising your firm's response to time-sensitive compliance events.

Incoming webhooks are a way to post messages from Gladius Regulatory Hub into Slack. Creating an incoming webhook gives Gladius Regulatory Hub a unique URL to which to send a JSON payload with the message text and some options.

We're going to walk through a 3-step process that will allow the Gladius Regulatory Hub to post messages using incoming webhooks in just a few minutes:

Create an app

• Pick From scratch
• Insert the following App Name: Gladius CASS Hub
• Choose a workspace to associate your app with, then click Create App.

• Go to Basic Information
• In Display Information, enter Short description CASS 15 Safeguarding
• Download Gladius App icon Icon and upload to +Add App Icon in the App icon & Preview section
• Save Changes

Under the Features menu on the left, select Incoming Webhooks, and toggle Activate Incoming Webhooks to ON.

Now that incoming webhooks are enabled, the settings page should refresh and some additional options will appear. One of those options is a very helpful button called Add New Webhook — click it!

What this button does is trigger a shortcut version of the installation flow for Slack apps, one that is completely self-contained so that you don't have to actually build any code to generate an incoming webhook URL. You'll see something like the following:

Go ahead and pick a channel that the app will post to, then select Allow. If you need to add the incoming webhook to a private channel, you must first be in that channel in order to view the notifications.

You'll be sent back to your app settings, where you should see a new entry under the Webhook URLs for Your Workspace section. Your webhook URL will look something like this:

https://hooks.slack.com/services/T0000000000/B0000000000/XXXXXXXXXXXXXXXXXXXXXXXX

That URL is the new incoming webhook, one that's specific to a single channel that you choose for Gladius Regulatory Hub to post notification. You can now copy and enter this link into the Slack Integration section of the Gladius Regulatory Hub.

To ensure a smooth setup, we recommend that firms and clients coordinate with their internal Slack Administrator or IT Support team before attempting to activate the integration. While the Gladius Regulatory Hub makes the technical connection straightforward, the ability to create and manage Incoming Webhooks is often restricted to users with appropriate privileges to maintain workspace security. Your Slack admin can assist in generating the unique Webhook URL, assigning it to the correct restricted channel, and ensuring the integration aligns with your organisation’s broader Data Governance and Cybersecurity policies.

Though in most cases Gladius Regulatory Hub will receive a “HTTP 200” response with a plain text ok indicating that the message posted successfully, it's best to prepare for scenarios where attempts to publish a message will fail.

Incoming webhooks may throw errors when receiving malformed requests, when utilized webhook URLs are no longer valid, or when something truly exceptional prevents our messages from making it through to your Slack channels and users.

Incoming webhooks return more expressive errors than Slack's Web API, including more relevant HTTP status codes (like “HTTP 400 Bad Request”, “HTTP 403 Forbidden”, and “HTTP 404 Not Found”). These are described in Slack's changelog: Changes to errors for incoming webhooks.

Errors we may encounter include:

• action_prohibited: An admin has restricted this avenue of posting.
• channel_is_archived: The channel is archived.
• invalid_payload: The JSON is structured incorrectly or text is not properly escaped.
• invalid_token: The token was expired, invalid, or missing.
• no_active_hooks: The incoming webhook is disabled.
• no_service: The incoming webhook is disabled, removed, or invalid.
• no_service_id: The service_id was invalid or missing.
• no_team: Workspace was missing or invalid.
• no_text: The text attribute was missing from the payload.
• posting_to_general_channel_denied: Posting to #general is restricted.
• team_disabled: The Slack workspace is no longer active.
• too_many_attachments: Thrown when a message has greater than 100 attachments.
• user_not_found / channel_not_found: The destination does not exist.

Source: Slack Sending Messages Using Incoming Webhooks