Postman

Read collection metadata and create named empty collections in a selected developer workspace.

Connect API delivery work to sales, support and implementation workflows.

Build a flow with Postman Provider API documentation

Source actions

Destination actions

Data types

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

api collections

Create empty API collection
Destination
Not retried automatically
Create a named collection in the selected workspace; does not execute requests or scripts.
Read API collections
Source
Read collection names and identifiers visible to this API key in the selected workspace.

Authentication

Postman API key

Plans and access

Postman account with API allowance. Key owner needs access to the selected workspace and permission to create collections.

Test environment

Use a dedicated development workspace, not production collections.

Rate limits

Respect Postman API plan limits and 429 Retry-After responses.

Provider events

Postman webhooks are not used by these operations. Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

Collection metadata only: no credential-bearing request bodies, environment values, script execution or public publishing.
Collection creation is not idempotent; reconcile a timeout before retrying.
An invalid workspace may return an empty list; a successful connection test confirms API-key access, not workspace ownership.
Credential-backed validation remains pending.