APer-pair page

Connect Slack to AWS Bedrock in two minutes.

Real-time triggers from Slack, ready-made actions in AWS Bedrock. Filter, transform, and route without writing a line of code.

Connect Slack and AWS Bedrock See reverse direction

Trigger app

Slack as the trigger

Workflows fire when something happens in Slack.

See all 13 triggers →

Action app

AWS Bedrock as the action

Workflows do something in AWS Bedrock, instantly.

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

ASlack → AWS Bedrock

When something happens in Slack, do it in AWS Bedrock.

13 Slack triggers wired to 3 AWS Bedrock actions. Most-used pairing: App Home Opened → Bedrock Converse.

AAWS Bedrock → Slack

Or fire it the other way around.

0 AWS Bedrock triggers wired to 45 Slack actions downstream.

Use any trigger in the catalog as the upstream.

See AWS Bedrock → Slack →

Popular pairings

Common Slack → AWS Bedrock workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 39 combinations

When app home opened in Slack, bedrock converse in AWS Bedrock.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, invoke model (raw) in AWS Bedrock.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app home opened in Slack, knowledge bases retrieve in AWS Bedrock.

Fires when a user opens your Slack app's Home tab or DM. Useful for refreshing the Home view, lazy-loading user-specific data, or tracking app engagement.

When app mentioned in Slack, bedrock converse in AWS Bedrock.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, invoke model (raw) in AWS Bedrock.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When app mentioned in Slack, knowledge bases retrieve in AWS Bedrock.

Fires when your Slack app is mentioned in a message. The standard hook for chatbots that answer when summoned with @your-app.

When new channel in Slack, bedrock converse in AWS Bedrock.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

When new channel in Slack, invoke model (raw) in AWS Bedrock.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

When new channel in Slack, knowledge bases retrieve in AWS Bedrock.

Fires when a new Slack channel is created in the workspace. Useful for auto-adding the bot, welcome messages, or governance audit logs.

How it works

Connect Slack and AWS Bedrock in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Slack and AWS Bedrock
Open Tiny Command, authorize Slack and AWS Bedrock once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Slack trigger
Drop the Slack → App Home Opened trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/slack.trigger-app-home-opened
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the AWS Bedrock action
Drop the AWS Bedrock → Bedrock Converse action below it. Map fields from the Slack payload into the AWS Bedrock inputs.
bedrock.converse
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Slack + AWS Bedrock.

How long does it take to connect Slack and AWS Bedrock on Tiny Command?

Under two minutes. Authorize Slack and AWS Bedrock once each, drop the Slack trigger and AWS Bedrock action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Slack ↔ AWS Bedrock integration real-time?

Yes. Both Slack and AWS Bedrock expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between Slack and AWS Bedrock?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit AWS Bedrock.

What Slack events can trigger a AWS Bedrock workflow?

Any of the 13 Slack triggers, including "App Home Opened". Each fires in real time when the matching event happens in Slack.

Do I need a paid plan to use Slack with AWS Bedrock?

No. There's a free tier that covers most Slack+AWS Bedrock use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want AWS Bedrock → Slack instead?

Build it the same way, in reverse. There's a dedicated /integrations/bedrock/with/slack page with the reverse-direction triggers and actions.

Other apps that pair well with Slack.

Slack + Gmail

Slack + Google Sheets

Spreadsheets & Databases

Spreadsheets & Databases

Wire Slack to AWS Bedrock in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo

Connect Slack to AWS Bedrock in two minutes.

Pick the way that fits your stack.

When something happens in Slack, do it in AWS Bedrock.

Or fire it the other way around.

Common Slack → AWS Bedrock workflows.

Connect Slack and AWS Bedrock in five steps.

Questions about Slack + AWS Bedrock.

Other apps that pair well with Slack.

Wire Slack to AWS Bedrock in 2 minutes.

Be the first to know what's next.