Custom apps let your workspace use its own Slack or Salesforce OAuth client. Open Settings → Integrations → Custom apps to add an app, manage its settings, and connect accounts through it.
Apps and Connections
An app registration stores the provider configuration and allowed permissions. Each connection authorizes an account or installation through that app.
| Resource | Purpose | Access |
|---|---|---|
| Custom app | Client configuration, permissions, and Slack manifest | App permissions control who can manage it or connect through it |
| Slack bot installation | Post as the app and receive bot events for a Slack workspace | Workspace resource; permitted workflow editors can use it, subject to explicit denies |
| Personal Slack connection | Perform actions as the person who connected | Only that person can use its user token |
| Salesforce connection | Access the connected Salesforce account through the custom client | Credential permissions control its use |
Sharing an app does not share every account connected through it. Bot credentials can also be shared with members or groups through credential access controls. Personal Slack tokens stay private.
Custom apps lists active registrations by default. Use the status filter to include disabled or archived apps. Archived app details are read-only. Each Slack bot shows its workspaces and where setup stands: Live after a successful test, Installed, Needs approval in Slack, Slack needs your changes, or Setup with the number of completed steps. People who cannot manage the bot see Not ready yet instead of setup steps.
Set Up Slack
Select Create custom app. Setup opens in five steps. A step is marked complete only after Slack confirms it, and the preview shows how the bot appears in Slack. Turn on Slack details to see event IDs, scope identifiers, and the manifest JSON.
- Design. Name the bot and choose what it listens for and what it can do. With Slack details on, each choice lists the Slack events and permissions it adds. Select Add more permissions for other bot actions for permissions outside these choices.
- Create. Select Create in Slack. Slack opens with the bot name, permissions, events, redirect URL, and events URL already filled in. Pick the workspace, then select Next and Create. Slack notes that the settings came from a third party and may mention token rotation. Both notes are expected. Return to SteelEngine and enter the App ID, Client ID, Client Secret, and Signing Secret from Slack's Basic Information page, then select Save and continue. Secrets are stored securely on save and are excluded from browser drafts. New apps default to PKCE; existing apps retain their saved OAuth setting, except that local callbacks require PKCE.
- Events. Slack checks the events URL when it creates the app, before the keys are saved, so the first check fails. Select Open Event Subscriptions and select Retry next to the Request URL. The step completes when Slack's check reaches SteelEngine. Use a public HTTPS origin for events and installation.
- Install. Select Add to Slack workspace and approve the permissions. Workspace administrator access is required. The installation shows the Slack workspace name.
- Test. Choose a channel the bot belongs to and select Start listening. If the bot is not in the channel, setup shows how to invite it, for example
/invite @Atlas. Send@<bot name> helloin that channel. Setup reports success only after receiving a matching signed event. A test stops listening after 15 minutes. You can select Finish without testing; the app remains marked as not tested.
Update Slack After Changes
Slack keeps its own copy of the bot's settings. After you save a change to the bot's name, events, or permissions, setup shows Slack needs your latest changes. Update Slack in one of two ways:
- Copy and paste. Select Copy settings, open App Manifest in Slack, replace its contents, and save. If permissions were added, select Approve in Slack to approve them for each installation. Then select I’ve updated Slack. This records your confirmation; event verification remains a separate status.
- Automatically. Select Update automatically instead. In Slack, open Your Apps, find Your App Configuration Tokens, and generate a token for the app's workspace. Paste the access token and refresh token, then select Save token and review changes. SteelEngine reads the app from Slack and lists what will change. Select Update Slack now to apply it. The token is stored encrypted and refreshed automatically. Select Remove saved token to delete it.
Slack does not remove a permission from an installed bot when you turn it off. The installation keeps it until the app is removed from that Slack workspace and added again. SteelEngine shows these permissions on the installation and does not ask you to reconnect for them.
Existing Slack Apps
On the first step, select Already have a Slack app?. In Slack, open the app's App Manifest, select Copy to Clipboard, paste the JSON, and select Read this app. SteelEngine keeps the app's other features and changes only what you choose. A conflicting event receiver or Socket Mode setting blocks the update; use a separate Slack app to preserve the existing integration. Changes to bot identity or irreversible settings require explicit confirmation.
Personal Actions
After a bot installation is available, open Personal Slack actions on the app and choose Connect my account to authorize your own user token when needed. Other members connect their own accounts.
In a Slack action block, select the app under Auth connection, choose Act as, then choose the matching credential. Select App bot to act as the installation or the connected-user option to act as yourself. If you have no personal connection, the block offers OAuth connection. Operations, destinations, and channel choices reflect the selected token's permissions.
Events and Channels
Managed Slack triggers use bot installations. Select the hosted app or a custom app, its bot credential, and one or more events from the app's saved subscriptions. Personal user-event triggers are unsupported. Change older user-event or combined-event triggers to a bot installation and redeploy them.
All workflows for a custom app receive events through its saved Events API URL, /api/integrations/apps/{routingKey}. Hosted Slack uses /api/integrations/slack/events. SteelEngine verifies signatures, matches the app and Slack workspace to the installation, and routes matching events to deployed workflows. The hosted endpoint requires SLACK_SIGNING_SECRET and uses the app ID from the verified payload; no hosted SLACK_APP_ID setting is needed. Trigger filters do not change the Slack manifest.
Use Events to match to choose multiple events, or select All events. A trigger matches any selected event within its channel and access restrictions. Use channels, message-change handling, and file handling to narrow each trigger. Channel controls distinguish visible channels from channels the selected identity can access. Join an eligible channel when the token has permission, or follow the invitation instructions. Receiving events also requires the channel to be allowed by the connection's policy and included in the app's subscriptions. Joining a channel does not automatically enable its events.
Enterprise Grid organization-wide installations and Slack Connect external shared-channel events are unsupported.
Connection Needs Attention
If a bot installation shows Needs approval in Slack, the saved configuration asks for permissions the installation does not have. Select Approve in Slack to approve them.
If Slack cannot verify the Events API URL, check that the saved signing secret belongs to the same app and that the public URL reaches SteelEngine.
Set Up Salesforce
Add a Salesforce custom app using your External Client App or existing Connected App. Copy the redirect URL shown by SteelEngine into the provider configuration, enter the consumer key and secret, and choose the production, sandbox, or HTTPS My Domain login environment.
Select the required permissions, save the app, and connect an account through it. The default permissions are api and refresh_token. Workflow and connector credential choices remain bound to the selected app and account. Changing client identity or login environment requires a new registration.
Local Development with a Tunnel
Start an HTTPS tunnel to port 3000. Stop the existing web process on that port, then start the web app from the repository root:
bun run dev:web:public -- https://your-tunnel.ngrok-free.appThis command sets NEXT_PUBLIC_APP_URL and APP_URL for the web process and keeps internal API calls on localhost unless INTERNAL_API_BASE_URL is already set. It does not edit environment files or start the rest of the local stack. Keep your usual infrastructure and worker services running.
Open the tunnel URL and sign in there before starting setup. Setup builds the manifest from that origin; for an existing app, update its redirect and Events API URLs through Slack needs your latest changes. Begin and finish authorization in the same browser session and origin.
For the deployment-wide hosted Slack app, see Slack Events.