Connect a Postman API key to check your work
You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.
Deploy the Mock by Asking
A local mock only helps you. Deploying it gives teammates and CI a URL. In the CLI module that took a push, a deploy and a get. Now you describe the outcome and the agent works out the commands. Your Postman account is changing here, so read what the agent proposes before you approve it.
-
Send this prompt, with a slug that is unique to you:
Push the Tasks mock to my bound Postman workspace and deploy it publicly with the slug `tasks-mock-<your-name>`. Then call `GET /tasks` on the live URL to check it works, and give me the mock URL.
-
Paste the mock URL below and click Validate. LiftOff finds your mock through the Postman API, checks that the URL belongs to it, and sends a
GET /tasksrequest.
Troubleshooting: A 401 means the mock was deployed private. Ask the agent to re-deploy it with public access. A URL that LiftOff can't match to your workspace usually means the mock was pushed to a different workspace, so ask the agent which workspace it used.
Have the Agent Add CI
The checks you ran by hand can run on every pull request. The plugin's ci-integration skill knows the right shape for this: install the CLI, log in from a secret, lint the spec and gate on readiness. You'll hand over the goal, and keep the one step the agent shouldn't do for you, which is storing the secret.
-
Add your Postman API key as a repository secret yourself, so it never passes through a chat. Run this on its own and paste the key when prompted:
gh secret set POSTMAN_API_KEYgh secret set POSTMAN_API_KEY -
Because your repo is a fork, GitHub disables Actions by default. Open the repo's Actions tab and click I understand my workflows, go ahead and enable them before the workflow is pushed, or the run won't start.
-
Send this prompt:
Add a GitHub Actions workflow at `.github/workflows/postman.yml` that runs on pushes to main and on pull requests. It should install the Postman CLI, log in using the `POSTMAN_API_KEY` repository secret, lint `openapi.yaml`, and fail if the AI readiness score is below 70. Never put the key in the file. Then commit and push it to main.
-
Watch the run:
gh run watchgh run watch
Troubleshooting: If the lint step fails, it's reporting a real problem in the spec, so ask the agent to read the log with gh run view --log-failed and fix it. If login fails, check the secret name matches exactly.
Let the Agent Open the Pull Request
A gate is only convincing once you've watched it react. You'll ask the agent to make a breaking change to the contract on a branch, so you can see how the plugin and your new CI behave together, and finish by reviewing a pull request rather than a chat transcript.
-
Send this prompt:
Create a branch called `feature/rename-title-to-name`. On it, make a breaking change to `openapi.yaml` by renaming the `title` property of `NewTask` to `name`. Run the spec lint and `postman workspace diff` and tell me what they report. Then commit, push the branch and open a pull request. Don't merge it.
-
Read the report, then the pull request. The agent should have described what the lint and diff found, and
gh pr checksshows how your workflow responded:gh pr listgh pr listgh pr checksgh pr checksgh pr diffgh pr diff -
Leave the pull request open.