What is Workbot for Slack?
Workbot for Slack is the Workato component that allows you to monitor and interact with your business apps from within Slack. Workbot posts notifications to Slack channels when important events happen, retrieves information from your apps, and creates or updates business data when users send it commands. Workbot is powered by Workato recipes: a command that a user sends in Slack triggers a recipe, and the recipe replies in Slack.
A standard Workbot is a bot that you connect to Slack without a custom OAuth profile, so it uses the default name, logo, and permissions. Workato supports only one standard Workbot per Slack workspace. An Enterprise Workbot is a bot that you connect via a custom OAuth profile, allowing you to use your own Slack app with your own name, logo, and permissions. It is required for Slack Enterprise Grid and for running multiple Workbots in the same Slack workspace.
Before you open a ticket
First, check status.workato.com and slack-status.com for ongoing incidents. If there is one, follow its updates and check the affected functionality again once it is resolved.
The following actions often resolve the most common Workbot for Slack issues, or help you work around them:
1. Check the recipe job
If Workbot replies with a recipe execution error, open the recipe that runs the command, find the failed job, and read the error. Fix the cause shown in the job and run the command again.
2. Check that Workbot can receive your command
- Workbot must be a member of the channel. Invite it by mentioning
@workbot(replaceworkbotwith the name of your bot) or by using the Invite new members to join option in the channel details Enterprise Workbot does not require an invitation - In a channel, start the command with
@workbot. In a direct message, you do not need it - Try the same command in a direct message with Workbot. This shows whether the issue is specific to the channel
3. Reconnect Workbot if it appears offline
Sometimes Workbot appears offline even though the recipe and the connection are active. This could be a temporary issue, so wait and try again. If Workbot stays offline, go to Connections, find the Workbot for Slack connection, disconnect it, and connect it again.
4. Check the request URL of your Enterprise Workbot
If a command of an Enterprise Workbot does not trigger a recipe, do the following:
- Go to Tools > Custom OAuth profiles, then select your bot's profile
- Copy the request URL that contains
/actions - In your Slack app, open the Interactive Components section and make sure the request URL is the same. If it is not, update it
If you use Slack Enterprise Grid, install the bot at the organization level, not in a single workspace.
5. Check the installation
If you see the error “Slack team already has Workbot installed”, another standard Workbot for Slack connection is already active in the Slack workspace. Contact the user listed in the error and ask them to remove the existing connection, connect a different Slack workspace, or use an Enterprise Workbot. If the installation is blocked for another reason, ask your Slack administrator whether you are allowed to install apps, because some organizations restrict this to administrators.
Information to include
If the issue persists, open a ticket and mention what you tried. Including the following information in your ticket helps Workato Product Support resolve it faster:
- Details of the issue
- Workbot details
- Recipe ID and job ID (for recipe execution errors)
- Slack details
- Workspace ID
- HAR file (for issues in the Workato UI)
- Screenshots
How to collect it
Details of the issue
Describe the following:
- The exact command that you sent to Workbot.
- Detailed steps to reproduce the issue.
- What you expected to happen and what happened instead.
- The exact error message or Workbot reply, if any.
- Timestamp of the last occurrence, with time zone.
- How often the issue occurs.
- Whether the issue affects all users or only some of them.
- Any recent changes.
- Whether it worked before or is a new setup.
Workbot details
- The name of the Workbot for Slack connection, which you can find in App Connections
- The type of Workbot: standard or Enterprise. If you are not sure, open the connection in App Connections. A connection with a custom OAuth profile selected is an Enterprise Workbot
- The name of the custom OAuth profile, if the connection uses one. You can find it under Tools > Custom OAuth profiles
- Whether your organization uses Slack Enterprise Grid
Recipe ID and job ID
If Workbot replies with a recipe execution error:
- Open the recipe that runs the command
- Copy the recipe ID from the browser address bar
- Click the Jobs tab, open the failed job, and copy the job ID
Slack details
Include the following:
- The name or URL of the Slack workspace
- Where you talk to Workbot: a direct message, a public channel, or a private channel
- Whether Workbot is a member of that channel
Workspace ID
Each environment (Development, Test, Production) has its own workspace ID. Provide the ID of the environment where the issue occurs. To find it:
- Open the environment where the issue occurs
- Navigate to Workspace Admin > Settings > General
- Copy the Workspace ID value
HAR file
A HAR file is a recording of your browser’s network traffic. It helps Product Support investigate issues that you can reproduce in the Workato UI.
Open browser developer tools:
F12orCtrl+Shift+I(Windows/Linux),Cmd+Option+I(macOS)Open the Network tab
Optionally select Keep log (called Preserve log in some browser versions)
Reproduce the issue
Click the Export HAR (down arrow) icon and save the file
- Attach the file to your ticket
A HAR file can contain sensitive data, such as authorization tokens, cookies, and the contents of your Workato pages. Share it only through the ticket.
Screenshots
Screenshots of the following help Product Support investigate the issue:
- In the Slack admin console, take a screenshot of the Workbot configuration settings
- In the Slack client, take a screenshot of the conversation with Workbot that shows your command, the reply, and the time of the message
- In the Workato UI, go to the page where the issue occurs and take a screenshot of the full browser window, so that the error and the address bar are both visible
Do not include the Client secret, the Verification token, or any other credentials from your Slack app settings.
Comments
0 comments
Please sign in to leave a comment.