slack-workflow-builder
Provides guidance for Slack Workflow Builder steps that interface with Salesforce.
Install
mkdir -p .claude/skills/slack-workflow-builder && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16330" && unzip -o skill.zip -d .claude/skills/slack-workflow-builder && rm skill.zipInstalls to .claude/skills/slack-workflow-builder
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use this skill when designing or troubleshooting Slack Workflow Builder workflows that call Salesforce — especially the Salesforce connector step Run a Flow, mapping inputs/outputs, handling failures, and understanding limits. Triggers on: Slack Workflow Builder Salesforce, Run a Flow from Slack, autolaunched flow from Slack, Slack automation calling Salesforce. NOT for Salesforce Flow Builder tutorials unrelated to Slack (use flow skills), not for Flow Core Actions that send Slack messages from Salesforce (use flow-for-slack), not for initial org-to-workspace connection (use slack-salesforce-integration-setup), and not for building custom Slack apps outside Workflow Builder.Key capabilities
- →Assist in designing Slack Workflow Builder automations that interact with Salesforce
- →Troubleshoot issues with the Salesforce connector step 'Run a Flow'
- →Guide on mapping input and output variables between Slack and Salesforce Flows
- →Provide operational guidance on throttling and asynchronous limits
- →Explain the distinction between Slack Workflow Builder and Salesforce Flow
- →Offer a review checklist for Slack-Salesforce workflow implementations
How it works
The skill provides context and core concepts for integrating Slack Workflow Builder with Salesforce, focusing on the 'Run a Flow' step, its prerequisites, supported Flow types, and operational limits. It also offers common patterns and a review checklist.
Inputs & outputs
When to use slack-workflow-builder
- →Fixing Slack-to-Salesforce workflow errors
- →Mapping data between Slack and Salesforce
- →Troubleshooting flow execution
About this skill
Slack Workflow Builder
This skill activates when a practitioner builds or debugs Slack Workflow Builder automations that touch Salesforce through the Salesforce connector. The connector offers five steps: Create a record, Read a record, Update a record, Delete a record, and Run a Flow. That path is distinct from Salesforce Flow calling Slack (Flow Core Actions such as Send Slack Message), which is covered by flow/flow-for-slack. This document covers the Slack-initiated direction: which flows Run a Flow accepts, whose Salesforce identity a step uses, and the governance and operational limits around it.
Before Starting
Gather this context before working on anything in this domain:
- Plan and approvals: Workflow Builder and connector steps are available on paid Slack plans, and workspaces that require app approval must approve the Salesforce connector before its steps appear.
- Target flow type: The Run a Flow step's flow picker is titled "Select a Flow (Only auto-launched flows are currently supported)" in Slack's connector schema. Screen and record-triggered flows are not valid targets, and the flow must be active.
- Identity: Connector steps authenticate to Salesforce with an account. The builder chooses whether everyone uses the builder's account or each person authenticates their own ("The person using the workflow"). That choice decides whose permissions every run uses.
- Audience: If the workflow will run in Slack Connect channels, external people can only use connector steps that do not require them to authenticate, and only when admins allow it.
Questions to Ask Before Configuring
| Question | Why it matters | What a good answer adds | What proper configuration adds over just doing it |
|---|---|---|---|
| "Does the Salesforce work start from a Slack action, or from a Salesforce record change?" | Slack-initiated work uses the connector; CRM-initiated work belongs in a Salesforce flow with Slack actions | The direction and the right product surface | No record-triggered logic forced through Slack |
| "Is a single record operation enough, or is logic needed?" | Create, Read, Update, and Delete steps need no flow; Run a Flow needs an active autolaunched flow | The simplest step that meets the need | Fewer flows to deploy and keep in sync with Slack |
| "Whose Salesforce account should each run use?" | With the builder's account, every run has the builder's permissions; with "The person using the workflow", each user authenticates and their permissions apply | An explicit identity decision per step | No accidental admin-level writes triggered by any channel member |
| "Who can start the workflow, including Slack Connect partners?" | External people cannot run connector steps that require their own authentication; admins control whether they can run any connector workflows | The audience and the Slack Connect setting | No partner running Salesforce writes under an internal account |
| "What happens when the flow is renamed, deactivated, or the builder leaves?" | Workflows reference the flow by name, and a builder who disconnects their account breaks steps that use it | An owner, a workflow manager list, and a deployment checklist | Workflows that survive releases and staff changes |
| "How often will it run, and what data returns to Slack?" | Every run is a Salesforce transaction, outputs post to whoever can read the channel, and activity logs keep only 90 days | A volume estimate and an output field list | No noisy channels, no leaked fields, and errors that are noticed |
What a proper configuration adds over "just adding the step": the target flow is autolaunched and active with explicit inputs and outputs, every run uses a deliberate identity, external use is governed, and Slack workflows are treated as dependents of the flows they call.
Core Concepts
Slack Workflow Builder vs Salesforce Flow
Slack Workflow Builder runs inside Slack. Workflows start from a link, a schedule, an emoji reaction, joining or creating a channel, or an external service, then chain Slack steps and third-party connector steps. Salesforce Flow runs inside Salesforce and can use Slack Core Actions. Workflow Builder pulls Salesforce work from Slack; Salesforce Flow pushes Slack updates from CRM events.
Salesforce Connector Steps
| Step (Slack connector function) | Inputs (required in bold) | Outputs |
|---|---|---|
Create a record (create_record) | salesforce_object_name, metadata (field values), salesforce_access_token | success, record_id, record_url |
Read a record (read_record) | salesforce_object_name, record_id, salesforce_access_token | record, salesforce_object_type, record_url |
Update a record (update_record) | salesforce_object_name, record_id, updates, salesforce_access_token | code, record_url, record_id |
Delete a record (delete_record) | salesforce_object_name, record_id, salesforce_access_token | code, record_id |
Run a Flow (run_flow) | flow_name ("Select a Flow (Only auto-launched flows are currently supported)"), metadata, salesforce_access_token | success, flow_name, result (Flow outputs) |
Source: the autogenerated connector schemas in Slack's slackapi/deno-slack-hub repository (src/connectors/salesforce/functions/*.ts) and the connector catalog in the Slack developer docs. The no-code step UI labels these fields differently.
Run a Flow
The step starts a Salesforce flow by name. The flow must be autolaunched and active. Input variables marked available for input appear as step inputs, and output variables come back in result for later Slack steps. If the flow is inactive, renamed, or not autolaunched, the step fails.
Identity and Governance
When a builder adds a connector step and clicks Connect, they can let everyone use their account or require "The person using the workflow" to authenticate. In coded workflows, the same choice is credential_source: "END_USER" (the end user authenticates, and the workflow must start from a link trigger) or "DEVELOPER" (a collaborator's account). Outputs posted to Slack are visible to everyone in the channel or DM.
Common Patterns
Pattern 1: Shortcut Form Runs an Autolaunched Flow
When to use: A Slack user fills a form and Salesforce should create or update records without opening Salesforce.
How it works:
- In Flow Builder, create an autolaunched flow with input variables (for example
opportunityId,taskSubject) and output variables for the confirmation. - Activate it and note the API name.
- In Workflow Builder, start from a link (shortcut), collect form answers, add Run a Flow, connect the Salesforce account, choose The person using the workflow when each user's permissions should apply, and map form fields to flow inputs.
- Add a Slack message step that uses the flow outputs.
Deployable flow metadata and a coded equivalent are in references/metadata-examples.md.
Why not a screen flow: The connector supports auto-launched flows only.
Pattern 2: Single Record Update Without a Flow
When to use: A Slack reaction or button should flag one record.
How it works: Use the connector's Update a record step directly with the object, record ID, and the field updates, and post the returned record_url back to the thread.
Why not Run a Flow: A flow adds a deployment dependency the single update does not need.
Decision Guidance
| Situation | Recommended Approach | Reason |
|---|---|---|
| Salesforce logic from a Slack trigger | Run a Flow on an active autolaunched flow | The connector supports auto-launched flows only |
| One record created, read, updated, or deleted | The matching connector step, no flow | Fewer moving parts |
| Slack message when a Salesforce record changes | Record-triggered Salesforce Flow plus Slack Core Actions | CRM is the event source |
| A user must work through screens | Screen flow in Salesforce or a Lightning URL | Not invocable from Run a Flow |
| Partners in Slack Connect must trigger Salesforce work | Prefer a Salesforce-side intake, or a connector step that does not need their authentication with admin approval and a least-privilege account | External people cannot authenticate connector steps |
Recommended Workflow
- Confirm the paid plan, the Salesforce connector approval, and the direction of the integration; if CRM-initiated, use
flow/flow-for-slackinstead. - Choose the step: a record step for single-record work, Run a Flow for logic.
- For Run a Flow, build or reuse an active autolaunched flow with explicit input and output variables, and record its API name.
- In Workflow Builder, connect the Salesforce account and set "Whose account should be used for this step" deliberately; map inputs and handle the failure path with a visible message.
- Set who can find and use the workflow, review the Slack Connect settings, and add workflow managers so the workflow survives staff changes.
- Run
python3 skills/integration/slack-workflow-builder/scripts/check_slack_workflow_builder.py --manifest-dir force-app/main/default, test with one user, then review the activity log (it keeps 90 days) after release.
Review Checklist
- Target flow is autolaunched and Active, with API name matching the Slack step
- Input variables are available for input; outputs are minimal and non-sensitive
- "Whose account should be used for this step" chosen deliberately and documented
- Slack Connect usage of connector workflows reviewed with the workspace owner
- Workflow managers added; Flow deployments include a Slack workflow check
- Failure path informs the Slack user
Salesforce-Specific Gotchas
One-line summaries; the full entries are in [`references/gotchas
Content truncated.
When not to use it
- →For Salesforce Flow Builder tutorials unrelated to Slack
- →For Flow Core Actions that send Slack messages from Salesforce
- →For initial org-to-workspace connection (use slack-salesforce-integration-setup)
Prerequisites
Limitations
- →The 'Run a Flow' step can invoke active autolaunched flows only
- →Salesforce-side automation posting to Slack is subject to asynchronous execution rules and org-wide throttles
- →Data returned from Salesforce into Slack should be treated as visible to everyone who can see the channel or DM
How it compares
This skill specifically addresses the interaction between Slack Workflow Builder and Salesforce Flows, clarifying the direction of integration and common pitfalls, unlike general documentation for either platform.
Compared to similar skills
slack-workflow-builder side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| slack-workflow-builder (this skill) | 0 | 7mo | Review | Intermediate |
| zendesk | 15 | 7mo | Review | Intermediate |
| zapier-workflows | 11 | 12mo | Review | Beginner |
| controlling-spotify | 7 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
zendesk
vm0-ai
Zendesk Support REST API for managing tickets, users, organizations, and support operations. Use this skill to create tickets, manage users, search, and automate customer support workflows.
zapier-workflows
davila7
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
controlling-spotify
oaustegard
Control Spotify playback and manage playlists via MCP server. Use when user requests playing music, controlling Spotify, creating playlists, searching songs, or managing their Spotify library.
smithery-ai-cli
smithery-ai
Find, connect, and use MCP tools and skills via the Smithery CLI. Use when the user searches for new tools or skills, wants to discover integrations, connect to an MCP, install a skill, or wants to interact with an external service (email, Slack, Discord, GitHub, Jira, Notion, databases, cloud APIs, monitoring, etc.).
connect-apps
ComposioHQ
Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.
freshdesk-automation
sickn33
Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.