Use Claude, Codex or MCP
Ask your AI app to build a workflow. You review it before it goes live.
Your AI app can create, test and publish workflows for you, using the same steps as the canvas. You copy a prompt, it does the work, and you check the result in Stacklink.
Connect your AI app
Follow Connect your agent. When asked, allow it to create and manage workflows. If you connected before, you may need to reconnect to add this permission.
Ask for a draft
Copy this into Claude or Codex. It makes a draft and tests it, but doesn’t publish.
In my Stacklink project, create an editable workflow called “Ticket intake”.
If this is a workspace connection, list my projects and let me select one.
Use that project's returned projectRef for subsequent calls.
First call STACKLINK_WORKFLOWS with action “contract”.
Use its exact schemas; do not invent fields or tool names.
Accept a required string input ticketId. Connect Start to Return a result,
returning the ticketId. Set source to visual. No apps, code, AI steps or triggers.
Validate, save the draft and simulate with {"ticketId":"ticket-42"}.
Inspect the run until it finishes or needs attention. Show its result,
workflow ID, run ID and dashboard link. Do not publish or start a live run.You should get a draft, a test that returned "ticket-42", and a link to open it in Stacklink.
Check it, then publish
Open the link and look at the steps. When you’re happy, ask:
Load the current draft of the Ticket intake workflow we just created.
Show what will go live, including triggers, then publish that revision.
Run it with {"ticketId":"ticket-42"} and jobKey “ticket-intake-live-42”.
If submission times out, reuse that key and identical input.
Inspect the result and show the run link. Do not add a schedule.Add a Bot to one step
Edit the existing Ticket intake workflow; do not create another one.
Discover my available published Bots. Ask me which assessor to use.
Add a Bot step with explicit mapped input and a structured answer.
Simulate with a supplied sample answer. Keep the change as a draft.
Do not run the Bot live, connect an account or publish yet.Your AI app still needs permission
It can only see and change what your account can. A Stacklink Bot can run workflows attached to it, but can’t create or publish them.
Tool actions at a glance
| Goal | Action |
|---|---|
| Exact schemas | contract |
| Draft | create, get, update, suggest, validate |
| Find exact references | search_mentions, resolve_mentions |
| Test or run | run |
| Publish | publish |
| Triggers | save_trigger, preview_schedule |
| Inspect | runs, get_run, events |
| Recover | action |
OAuth MCP supplies its authenticated session. SDK callers supply sessionId themselves. A project connection already selects its project; a workspace connection uses STACKLINK_LIST_PROJECTS and the returned projectRef.