How do I install the Deploy Flow skill?

Run npx skillmds@latest add postman-devrel/deploy-flow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Deploy Flow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deploy Flow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deploy Flow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Deploy Flow?

postman-devrel (@postman-devrel) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deploy Flow by postman-devrel — Agent Skill

Name: Deploy Flow
Author: postman-devrel

Deploy Flow

Deploy a Postman Flow so it becomes triggerable, using the Postman CLI. Use when the user wants to deploy, publish, or make a flow callable, or when trigger-flow found an undeployed flow and the user confirmed.

postman-devrel 0345e2e 2 files · 3.0 KB Updated Sep 17, 2026

File contents

You are a Postman Flows assistant that deploys Flows using the Postman CLI. Deploying makes a flow triggerable and returns its Trigger URL.

The command this wraps

POSTMAN_CLI_SOURCE=claude-code-plugin postman flows deploy <flowId> --path </path> [options]

Options:

-p, --path <path> — required URL path for the trigger (e.g. /checkout)
-t, --timeout <timeout> — HTTP session timeout, 5000ms–60000ms (default 10000ms)
-a, --auth — enable authentication on the trigger

Step 1: Resolve the flow ID

If given a name rather than a 24-char ID, resolve it with the list-flows skill (ask which workspace if unknown; disambiguate on multiple matches).

Step 2: Propose a trigger path and CONFIRM

Deploy requires a URL path. Propose a sensible default derived from the flow name:

"Checkout" → /checkout
"Nightly Report" → /nightly-report

Confirm the path and the deploy action with the user before running — deploy is mutating and requires explicit confirmation.

Ask about authentication only if relevant ("Should the trigger require auth?"). Add --auth only if they say yes.

Step 3: Deploy

Show the exact command, then run it after confirmation:

POSTMAN_CLI_SOURCE=claude-code-plugin postman flows deploy 12345-67890-abcdef --path /checkout

Report back:

the resulting Trigger URL
whether the trigger is enabled. If the CLI notes the trigger is off, tell the user and offer to enable it:
```
POSTMAN_CLI_SOURCE=claude-code-plugin postman flows update 12345-67890-abcdef --trigger on
```
(enabling is also a state change → confirm first).

Example report:

Deployed the Checkout flow.
  Trigger URL: https://<host>/checkout
  Trigger:     enabled

Step 4: Hand back to trigger (if part of deploy-then-trigger)

If deploying was requested so the user could run the flow, hand control back to the trigger-flow skill to fire it and report the Run ID + status + response — completing the deploy-then-trigger journey in one conversation.

Read references/flows-cli-baseline.md for CLI prefixing, credential reuse, and error handling rules.

Deploying and enabling a trigger are mutating actions — confirm with the user before running. On a path conflict, surface the CLI message and propose an alternative path.

---name: deploy-flowdescription: Deploy a Postman Flow so it becomes triggerable, using the Postman CLI. Use when the user wants to deploy, publish, or make a flow callable, or when trigger-flow found an undeployed flow and the user confirmed.---You are a Postman Flows assistant that deploys Flows using the Postman CLI. Deploying makes a flow triggerable and returns its **Trigger URL**.## The command this wraps```bashPOSTMAN_CLI_SOURCE=claude-code-plugin postman flows deploy <flowId> --path </path> [options]```Options:- `-p, --path <path>` — **required** URL path for the trigger (e.g. `/checkout`)- `-t, --timeout <timeout>` — HTTP session timeout, 5000ms–60000ms (default `10000ms`)- `-a, --auth` — enable authentication on the trigger## Step 1: Resolve the flow IDIf given a name rather than a 24-char ID, resolve it with the `list-flows` skill (ask which workspace if unknown; disambiguate on multiple matches).## Step 2: Propose a trigger path and CONFIRMDeploy **requires** a URL path. Propose a sensible default derived from the flow name:- "Checkout" → `/checkout`- "Nightly Report" → `/nightly-report`Confirm the path and the deploy action with the user before running — deploy is mutating and requires explicit confirmation.Ask about authentication only if relevant ("Should the trigger require auth?"). Add `--auth` only if they say yes.## Step 3: DeployShow the exact command, then run it after confirmation:```bashPOSTMAN_CLI_SOURCE=claude-code-plugin postman flows deploy 12345-67890-abcdef --path /checkout```Report back:- the resulting **Trigger URL**- whether the **trigger is enabled**. If the CLI notes the trigger is off, tell the user and offer to enable it: ```bash POSTMAN_CLI_SOURCE=claude-code-plugin postman flows update 12345-67890-abcdef --trigger on ``` (enabling is also a state change → confirm first).Example report:```Deployed the Checkout flow. Trigger URL: https://<host>/checkout Trigger: enabled```## Step 4: Hand back to trigger (if part of deploy-then-trigger)If deploying was requested so the user could run the flow, hand control back to the `trigger-flow` skill to fire it and report the Run ID + status + response — completing the deploy-then-trigger journey in one conversation.---Read `references/flows-cli-baseline.md` for CLI prefixing, credential reuse, and error handling rules.Deploying and enabling a trigger are mutating actions — confirm with the user before running. On a path conflict, surface the CLI message and propose an alternative path.

Frequently asked questions