Workflow Builder & automations
Workflow Builder is fine for sending a welcome message, but anything real requires premium tiers, has tiny integration coverage and produces an admin-menu mess no one wants to maintain.
Ce que les utilisateurs disent vraiment
✕Workflow Builder lacks conditional logic beyond basic branching, has no data enrichment, and its app catalogue is under a hundred connectors — a fraction of Zapier's library.
Source : Xray, Slack Workflows vs automation giants ↗✕Engineers describe Workflow Builder as good for the simple cases but quickly hitting walls — flows are hard to test, hard to version, and break silently when Slack ships changes.
Source : Adam Leventhal, Workflow Builder review ↗✕Independent reviews flag Workflow Builder's scalability and maintainability as the main blockers — limited testing, limited integrations, hard to grow.
Source : Cotera, Slack automation tools guide ↗
Automations live as TypeScript jobs on Inngest or Trigger.dev — diffable in git, testable in CI, retried automatically. The Slack app side is a thin Bolt receiver that hands events off to your worker; no admin-panel archaeology, no premium-tier paywall to wire "if message contains link, post to #leads".