Shipfox

Route Slack requests to your workflows

Mention one Slack app for any request, and it starts the workflow that handles it.

Someone mentions the Shipfox app in Slack with any request

How it works

  1. Someone mentions the app in SlacktriggerThey ask a question, ask for a ticket, or ask for a change in a thread.
  2. The agent picks a workflowagentIt reads the thread and chooses one workflow from your list, such as codebase questions, Slack to ticket, or task to pull request. It asks when the request is unclear or an input is missing.
  3. The workflow starts the chosen workflowtoolIt posts the run link in the thread. A repeated request gets the earlier run.
  4. The result appears in the threadwriteThe chosen workflow replies with an answer or a ticket link. For a change, the dispatcher posts the pull request link.
  5. You review the resulthumanYou review and merge any pull request yourself.

What it writes

  • Shipfox
    • Starts one listed workflow per request.
  • Slack
    • Replies once in the thread, and later posts the pull request link for a change.

Before you start

  • Invite the Shipfox app to each Slack channel where it routes requests.
  • Set up each workflow it starts in the same project first. Set the codebase question and Slack ticket workflows to start only from another workflow.

Models

  • routetested with gpt-6-luna · high thinkingReads the Slack thread, picks one listed workflow, and writes its inputs, or asks for what is missing. A mid-sized model is enough.

When you set up this workflow, your coding agent suggests models that your workspace can use. You choose the model for each step.

Related examples

Was this page helpful?
Edit this page on GitHub