Flux in Slack
How to ask Flux about a Workfloor project from Slack, bind a channel to a project, turn a conversation into a card, and get updates and questions about your cards back in Slack.
Flux answers in Slack as well as in Workfloor. People ask it about their work in a direct message or a bound channel, ask it to make a card from a conversation, and hear back in Slack when a card needs them. The Flux chat in Workfloor is the same assistant.

/flux.Connect Slack
Three things are set up, by different people:
- Flux's Slack app is set up once for the whole Workfloor team.
- Your Slack account. Each person connects their own under Slack account in their account menu, so Flux knows who is asking. Workfloor never reads or posts as you in Slack. Until you connect, Flux answers with a link to do it.
- A channel's project. A Team admin binds a channel to a project in Settings > Connections > Slack channels, or in Slack: invite
@Flux, then/flux bind <project>./flux unbind <project>frees it from a project and/flux wheresays what it is bound to. A channel can serve several projects. When a thread could be about more than one, Flux asks which.
Ask Flux
- In a direct message, Flux answers from the project you last asked about. Name another project, a card's link or an issue such as
owner/repo#12to switch. - In a bound channel, mention
@Fluxin a thread. Everyone in the thread reads the answer, and Flux answers only people who are in the project. - With
/flux, in any channel, Flux answers only you.
Flux reads the project's board, cards, missions and Mission Control. In #sales-cloud-delivery, you might ask what is waiting on review. Flux lists the cards. You then ask it to open a task for a validation rule on Opportunity.
Flux acts as you, and only where you are allowed to act. Where it can act for you, it can make a card, open a GitHub issue, move a card, ask a card's agent something, or pin a thread to the Lounge. Anything that changes work waits for your go-ahead, shown as a button, and you answer each proposal on its own. In a thread, only the person who asked can answer. With /flux, the buttons are visible only to you. A proposal that waits more than 30 minutes lapses; ask again.
Flux does not give a step's Run in Slack. That is answered on the card in Workfloor, beside the change. Flux cannot see pictures yet, so send a few words with them.
Work coming in from Slack
When you ask for a card, Flux makes it in a lane of the project with you as its foreman. The card goes to the lane's first stage that takes new cards, unless you name another. In Slack, Flux writes a few lines that sum up the conversation as the card's description. If the project has several lanes or repositories, Flux asks which.
Support channels work differently. A triage channel starts cards from mentions and rules, and Flux investigates them. Support triage describes it.
Work coming back to Slack
- One thread per card. After Flux has messaged a card's agent from a thread, it follows the thread. Reply without mentioning Flux and the reply goes to the agent. The agent's answers, and the card's pull request opening or merging, come back to the thread.
- Questions. When a stage asks a question and the card has a Slack thread, Flux posts it there with its options as buttons and mentions the assignee. A click answers as the person who clicked, through the same checks as on the card. An approval has Approve and Decline. A person an approval names also gets a direct message with Approve and a link to decline in Workfloor, where a decline says why.
- When a card needs you. If your Slack is connected, Flux sends you a direct message when a card assigned to you needs you: it asks something, wants a permission, is ready for review, or has failed. You get one message for each time a card starts needing you.
- When an agent gives up. The post says what happened, with Try again where Workfloor can start the agent again, and Open card.
- A digest.
/flux digest at 09:00 weekdayssends you a daily digest of your work./flux digest offstops it.
Other posts in Slack
A routine posts only to the Slack channels its version names. Triage never uses a channel that is shared with another workspace.
Next
Follow the work from the card: Your first card.
Preview orgs and environments
Look at a Workfloor card's running change instead of only its diff, through the app the repository previews or an org or sandbox that Flux hands to the card.
Stage workbenches and scratch pads
How a Workfloor card's page changes with the stage it is in, what the Plan, Changes and Scratch pad views hold, and how Salesforce projects see metadata changes.