Card #1129 · Slack App Directory
Difficulty triggering external APIs and GH Actions via Slack Workflows
Merchants find it overly complex to trigger external actions, such as GitHub Actions, directly from Slack. The native Workflow Builder lacks the ability to hit external APIs, forcing users to build and maintain their own custom middleware servers to handle events and handshakes.
Pain score
0.48/ 1.00 · weighted product of four components
Reach0.50distinct authors (log-normalized)
Recency0.62freshness decay, half-life months
Engagement0.31upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 3 verified quotes
native Workflow Builder still can't hit external APIs.
There’s no way to trigger a app script with a slack workflow without the native Google integrations slack offers
We ended up deploying a small Express app on Railway just to bridge the two. It works, but now we own the infra, the uptime, token rotation, logs... for what should literally just be a text box in a config menu.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro