I need to send a POST request to a Slack webhook URL from my automation with a JSON body and Content-Type: application/json header.
I don’t have the Custom REST APIs connector available in my workspace.
Is there a supported way to make HTTP POST requests from an automation without the REST API connector? Or how can I get the Custom REST APIs connector enabled for my automation group?
Hi @unnatija ,
The REST API Connection connector isn’t on the “Available” tab where the pre-built connectors live. It’s under the “Create for your team” tab in the Connectors section of the console, and it needs to be manually configured. Creating connectors requires an Enterprise subscription, so if you’re on a Professional plan, the “Create for your team” tab will either be empty or you won’t have permission to add one. In that case, your admin would need to create it and share it with you.
To set it up: Console > Connectors > “Create for your team” tab > find “REST API Connection.” You’ll give it a name, choose service authentication (which is what Automations use for service-to-service calls), configure your Slack webhook URL as the base endpoint, set your Content-Type header, and publish it. Once it’s published, it’ll show up as an available action in your automation. The full setup walkthrough is here: REST API Connection integration - Amazon Quick
Additionally, it is worth noting that the REST API connector only works in Automations (not Chat Agents or Flows), and the native Slack connector doesn’t support Automations either. So the REST API route is actually the correct and only supported path for sending HTTP POST requests from an automation to a Slack webhook.
If you still don’t see it after checking the right tab, it might have something to do with what subscription tier you have.
Hi Jacob,
As suggested by you I have created the rest api for my team but I am not getting an option to integrate this with my automation.
Only getting option to try this connector in chat. I have given the necessary permission as well
Hi @unnatija,
The “try this connector in chat” button is just the connector’s built-in test interface. It exists for all connectors and doesn’t mean yours is limited to Chat.
The most common reason a connector doesn’t show up in the automation builder is that it hasn’t been added to an Automation Group. Creating the connector and setting permissions are separate steps from attaching it to the group where your automation lives. Go into your Automation Group settings and add the REST API connector there. Once it’s attached, it should appear in the Actions library (setup reference).
One other thing to verify: when you created the connector, did you select “Service authentication” or “User authentication”? Automations require service authentication since there’s no interactive user session at runtime. For a Slack webhook, the API key option works well since the webhook URL itself acts as the credential.
If the above doesn’t resolve it, can you state if you see any connectors in the Actions library inside your automation, or if it’s completely empty? Also, did you create the automation inside an existing Automation Group or as a standalone project?