Your First Workflow

Your First Workflow

This walkthrough takes a real conversation and turns it into a tracked ticket, then shows you how to verify what happened and how to make it repeatable.

The Scenario

Your team has spent ten minutes in a channel working out that the login button fails on Safari after a session expires. The details are all in the thread, and none of them are in your tracker yet.

Step 1: Ask in the Thread

Reply in the thread rather than the main channel, so Quickly has the conversation as context:

@Quickly create a bug in MOBILE from this thread, priority High

Quickly reads the whole thread, not only the message that mentions it. It drafts a summary and a description from the discussion, and picks up the project key and priority you specified.

Step 2: Approve the Action

New workspaces run in Conservative autonomy mode, so anything that writes data stops for approval first. Quickly posts a confirmation card showing the action it intends to take, the key fields it will send, and why approval was required.

Tap Approve and the action runs. Tap Reject and Quickly cancels and offers to adjust the request. If nobody responds within five minutes the action times out, which is intentional: an unattended write should never fire hours later.

Step 3: Read the Result

Quickly replies in the thread with the issue key and a link. Anyone following the conversation can see the work was captured without leaving Slack, and the ticket carries the context from the discussion rather than a one-line summary typed from memory.

Step 4: Check the Log

Open Action Logs in the dashboard. Your request appears with the tools Quickly called, the outcome of each call, how long it took, and the link to the created issue. Each tool call is also labelled with the policy decision that allowed it: Auto, Needs approval, or one of the blocked states.

Step 5: Make It Repeatable

If you find yourself making the same request weekly, save it as a playbook instead of retyping it. Playbooks capture the steps, can be triggered on a schedule, and report their runs in the same logs. See Understanding Playbooks.

Tips That Change the Result

• Be specific about the parts that matter. "Create a High bug in MOBILE" produces a better ticket than "make a ticket", because Quickly does not have to guess the project or priority.
• Reply in the thread. Context comes from the conversation, so a top-level mention gives Quickly far less to work with.
• Say what the outcome should be, not which tool to use. Quickly selects tools from what you have connected.
• Loosen the guardrails once you trust the results. Most teams move from Conservative to Balanced after a week or two. See Autonomy Controls and Safety.