Slack Workflow Builder Plan for Routine Requests
Plan simple forms and automations before building them.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan Slack workflows for routine requests at [TEAM_NAME]. Requests that arrive by message today and what the team always asks back: [REQUESTS_AND_QUESTIONS]. Who handles them and where the result should go: [HANDLERS_AND_DESTINATION]. Tools connected to Slack: [CONNECTED_TOOLS]. For up to five workflows, choosing those that remove repeated questions and saying which requests should stay as a conversation, write: the trigger (a shortcut, a channel button or a schedule), form fields with types and which are required (personal data kept to the minimum [VERIFY policy]), who is notified, what is posted and where, the follow-up reminder, and what the workflow must not do. Give a plain-language description of the build steps, marked [VERIFY] where names or options may differ in our version. Rank by time saved with the assumption stated (20 requests a week at 4 minutes of back-and-forth each is 80 minutes). Test plan with two sample submissions, one incomplete, and the expected result. Say how to switch a workflow off and who owns it.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.