Need help connecting Quick to Slack so Quick can post in my Slack channels automatically

Q&A
,
1

Slack Admin Request — Enable Channel Posting for Amazon Quick Connector

Requested by: Emily Anderson (emilyea@amazon.com) — L5 Area Manager, EOL, PSP3 Date: 2026-09-30

What I need

I use the Amazon Quick Slack connector (“Operations Slack V2”) to send automated reminders and digests from a scheduled agent (the “PSP3 UPP Load Tracker”). Today the connector can only send me direct messages — it is blocked from creating channels and posting to channels, returning Access denied (400) even after reconnecting Slack and adding the Quick app to the target channel.

Please grant the Amazon Quick / Operations Slack V2 connector permission to post to channels (and ideally to post under a bot identity rather than as my own user).

Why it matters

  • The connector currently posts as my own Slack identity, so my self-DM reminders arrive already marked as read — they never show as unread, so I miss them during my shift.

  • I want the tracker’s digests to post to a channel so they show as unread where I actually work, and so I can share UPP load visibility with my co-manager and peers.

Target channel

  • Name: #psp3-reuseables-tracking (renamed from #psp3-upp-tracker)

  • Channel ID: C0C5A5LDZLK

  • The Amazon Quick app has already been added to this channel.

Specifically, one or both of:

  1. Channel-posting scope for the connector (chat:write to channels the app is added to), and

  2. A bot identity for the connector (so messages post as an app/bot, not as my user — this fixes both the “can’t post to channel” block and the “self-DM shows as read” problem).

Connector details (for the admin)

  • Connector: Operations Slack V2

  • ARN: arn:aws:quicksight:us-east-1:764946308314:action-connector/b7781413-fff0-4f89-89f0-421a4f9c31b0

  • Token status: VALID

  • DM posting: works reliably

  • Channel posting: DENIED — needs workspace-admin to grant channel-post scope

What already works (for reference)

  • The connector successfully sends DMs to me (self-DMs).

  • It is only channel create/read/post that is denied — pointing to a connector/workspace-level permission, not channel membership.

  • Confirmed the block persists after: reconnecting Slack in Settings, adding the Quick app to the channel, and signing into Slack in-browser. Only a workspace admin can lift it.

Thank you!

2

Hi @emilyea and welcome to the community!

Since this is a public facing forum, we do not have access to anyone’s account, nor do we have authority to grant permissions to people. I would highly recommend reaching out internally to whoever administers the Operations Slack V2 connector and your Slack workspace, since everything you’re asking for is an admin-side action rather than something configurable from your end.

Hope you get it sorted!