Contentful and Postman Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Keep Contentful and Postman matched by integrating their events and actions. When developer tools events happen in Contentful, update the Postman automatically - without any line of code in visual workflow builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Contentful and Postman
Detailed info you need to know about Contentful and Postman integrations in WEXTL. Explore which modules apps support and how you connect them.
Contentful

Headless CMS content management with spaces, entries, assets, content types, locales and publishing workflows.[5]
Postman

Manage Postman collections, environments, mock servers, monitors, specs and workspaces.[6]
How to connect Contentful to Postman
Set up your Contentful and Postman integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Contentful and Postman
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Contentful and Postman nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Contentful and Postman. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Contentful and Postman work in WEXTL?
WEXTL exposes actions and triggers for Contentful and Postman that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Contentful triggersPostman actions
Contentful modules
- Activate a Content Type Makes a content type active in the environment. Optimistic locking applies, so pass the Version read earlier. Output includes the Name, Display Field and Fields.
- Archive a Release Archives a release. Supply Version so Contentful can check for concurrent edits, and the response lists the Title and Entities of the release.
- Archive an Asset Archives an asset in the environment. Take the Version from an earlier read of the item, and the response returns its Fields.
- Archive an Entry Puts an entry into the archive. Pass Version from a prior Get to guard against overwriting newer edits. The response lists the Fields and Metadata of the entry.
- Cancel a Scheduled Action Cancels a scheduled action before its Scheduled For time arrives.
- Create a Comment Posts a new comment on an entry with the text from Body.
- Create a Content Type with POST Defines a content type from a Name and an array of Fields definitions. Use Display Field to choose which field titles the entries.
- Create a Delivery API Key Creates a Content Delivery API key under a Name with a Description. Use Environments to limit the environments the key reaches. The response includes an Access Token.
- Create a Locale Adds a language to the environment, identified by Name and Code. Use Fallback Code to name the locale it falls back to, and turn on Default or Optional to mark its role. Turn on Content Delivery API or Content Management API to expose it there.
- Create a New App Bundle Creates a build of an app definition from an app upload. Use Comment to label it and Upload to link the app upload it comes from.
- Create a New App Definition Registers an app in your organization with a Name. Use Source URL to point at the hosted app, and Locations and Parameters to describe where it shows up and what it can be configured with.
- Create a Personal Access Token Generates a personal access token for your own user. Use Name to label it, and add a Scope document to define what it may access.
- Create a Preview Environment Sets up a preview environment from a Name and an array of Configurations, one per content type. Use Description to say what it is for.
- Create a Release Starts a release titled by Title. Use Entities to begin it with entries and assets already included.
- Create a Role Defines a space role from a Name plus a Description. Add Permissions and Policies to spell out what its holders may do.
- Create a Scheduled Action for a Compose Page Schedules an action such as publish for a Compose page entry. Use Entity to link the entry and Environment to link the target. Use Scheduled For to set the date and timezone, and Payload for withReferences filters.
- Create a Signed Request Builds a signed request for an installed app from a Method plus a Path. Use Body to send a payload and Headers to add custom headers. The result carries Additional Headers with the signature data.
- Create a Space Creates a new space. Use Default Locale to start it with a locale code of your choice, such as en-US.
- Create a Space Membership Invites someone to a space by Email and gives them the Roles in the array. Turn on Admin to make the invited member a space admin.
- Create a Task Attaches a task to an entry, worded through Body. Use Status to set the initial state and Assigned To to link the user responsible.
- Create a Validation Release Action Checks whether a release can go through the publish or unpublish Action selected. The response lists the release Title and Entities.
- Create a Workflow Definition Defines a workflow from a Name, a Flow Type and an array of Steps. Use Applies To to list the content types and validations it covers, and turn on Start On Entity Creation to start it when an entity is created.
- Create an Action Registers an app action under a Name within a Category. Use Description to explain it and Parameters to define the inputs it takes.
- Create an App Upload Uploads the raw app build bytes of File to your organization. Output includes Uploaded From.
- Create an Asset Creates an asset from Fields that hold the title, description and file, each keyed by locale.
- Create an Asset Key Creates an asset key that expires at the Unix timestamp from Expires At. The result carries a Policy and a Secret.
- Create an Entry Creates an entry, filling it from Fields keyed by field ID and locale code. Use Content Type ID to say which content type it follows. Output also includes Metadata.
- Create an Environment from an Existing Environment Clones an existing environment into a new environment named by Name.
- Create an Environment Template Creates an environment template from a Name, a Version Name and the Entities it defines, such as content types and editor interfaces. Write a Description for the template and a Version Description for its first version.
- Create an Extension Registers an extension in the environment. It needs a Name, a Source URL and the Field Types it handles. Sidebar shows it in the sidebar.
- Create an Upload Resource Sends the raw bytes of File to the Contentful upload host of your region. Output includes Uploaded From.
- Create One Access Grant Grants an app definition access for a Grantee ID of a Grantee Type, which can be all or a single space.
- Create or Overwrite the App Signing Secret Stores a 64-character Signing Secret for an app definition, creating it or replacing the existing one. Include the sys.version of a previous Get as Version.
- Create or Update a Preview Environment Saves a preview environment at a Resource ID of your own, replacing what was stored there. Add a Name and Configurations for the content types, and use Description to explain it. Fetch it first and carry its sys.version over as Version.
- Create or Update App Details Saves the details of an app definition, currently an Icon object with a base64 value. Contentful locks optimistically, so use a Version from a prior Get.
- Create/update a Webhook Saves a webhook at a Webhook Definition ID of your own. It calls URL for each of the Topics. Add Filters or Headers to refine the call, turn on Active to switch it on, and fill the HTTP Basic fields for basic auth.
- Create/update an Asset Writes an asset to an Asset ID of your own. Fields hold the title, description and file by locale, and an existing asset at that ID is replaced.
- Create/Update an Environment Alias Points an environment alias at the Environment you link, under an Environment Alias ID of your own. Send a Version from a previous read.
- Create/update an Extension Writes an extension to an Extension ID of your own, with its Name, Source URL and Field Types. Reuse the revision number of a previous Get through Version. Turn on Sidebar to show it in the sidebar.
- Deactivate a Content Type Unpublishes a content type to take it out of the active state. The response lists its Name, Description and Fields.
- Delete a Comment Deletes a comment that someone left on an entry.
- Delete a Content Type Removes a content type definition from the environment.
- Delete a Locale Removes one locale from the environment.
- Delete a Preview Environment Deletes a preview environment that belongs to the space.
- Delete a Single Delivery API Key Removes a Content Delivery API key from a space.
- Delete a Single Role Deletes a role that was defined for the members of a space.
- Delete a Single Space Membership Removes a member from the space by ending the membership.
- Delete a Space Deletes the space you are working in. Only its Sys is reported.
- Delete a Tag Deletes a tag that exists in the environment.
- Delete a Task Removes a task attached to an entry.
Postman modules
- Add a Collection to an API Attaches collection content to an API from an Operation Type and Data (JSON). It returns the stored Data and Operation Type.
- Create a Collection Starts a collection in a workspace. Prefill it with Items (JSON), Variables, Auth (JSON) and Events (JSON), or add a Description. It returns the Id, Name and Uid.
- Create a Collection Comment Leaves a Comment on a whole collection. Use Thread ID to reply in an existing thread, and Tagged Users to mention people by User ID or Username.
- Create a Collection Folder Makes a folder in a collection from a Name. Use Parent Folder ID to nest it inside another folder.
- Create a Collection Pull Request Opens a pull request that proposes merging a forked collection into a Destination. Assign Reviewers, give it a Title and add a Description to explain the change.
- Create a Collection Request Saves an API request in a collection with its Method, URL, Headers, Query Parameters and body. Use Folder ID to file it in a folder, or add Auth (JSON) and Events (JSON).
- Create a Collection Response Stores an example reply under the request with the Request ID. Add Status Text, Headers and a Body, and use Body Language for the syntax of the Body.
- Create a Collection Webhook Sets up a webhook for a collection under a Name. Add an Environment to run the collection with.
- Create a Folder Comment Posts a Comment on one folder of a collection, using the Folder ID. Use Thread ID to answer an existing thread and Tagged Users to mention people.
- Create a Mock Response Defines a server response on a mock server from a Name. Use Headers, Language and Body to shape what the mock sends back.
- Create a Mock Server Spins up a mock server from a collection in a workspace. Pick an Environment, give it a Name, and set Private to restrict callers. It returns the Mock Url.
- Create a Monitor Schedules a collection run on a Cron expression in a Time Zone. Turn on Active to run it, and tune Retry Attempts, Notification Limit, Email on Error and Email on Failure.
- Create a Request Comment Writes a Comment on one request of a collection, using its Request ID. Reply in a thread with Thread ID or mention people through Tagged Users.
- Create a Response Comment Adds a Comment to a saved example, using its Response ID. Set Thread ID to continue a thread, or Tagged Users to mention teammates.
- Create a Spec Writes an API spec into a workspace from a Name, a Type and its Files. Each file carries a Path and its Content.
- Create a Spec File Puts another file into a spec at the Path of your choice, along with its Content. The new file returns with its Id, Created At and Created By.
- Create a Spec Version Tag Marks the current state of a spec with a Name, giving you a version to return to later.
- Create a Workspace Opens a workspace from a Name and a Type. Add context with Description and About, and assign it to a team through Team.
- Create a Workspace Update Publishes a post to a workspace with a Topic, a Description and a Category. Add Related Resources, each with a Resource and Resource ID, to link what it covers.
- Create an API Registers an API in a workspace from a Name, with an optional Summary and Description. The API is returned with those three values.
- Create an API Version Releases a version of an API from a Name. Link Schema IDs and Collection IDs to it, and add Release Notes to explain what changed.
- Create an Environment Builds an environment in a workspace from a Name. Add Variables, each with a Key, Value, Type, Enabled flag and Description, to start with values.
- Delete a Collection Deletes a collection, the saved set of folders and requests.
- Delete a Collection Comment Deletes the collection comment that carries a Comment ID.
- Delete a Collection Folder Removes the folder with a given Folder ID from its collection.
- Delete a Collection Request Deletes a single request from its collection, using Request ID.
- Delete a Collection Response Removes a saved example response from its request, using Response ID.
- Delete a Folder Comment Removes a folder comment by its Comment ID, from the Folder ID folder.
- Delete a Mock Response Removes a mock server response by Server Response ID.
- Delete a Mock Server Removes a mock server, the fake API backed by a collection.
- Delete a Monitor Removes a scheduled monitor from your Postman account.
- Delete a Request Comment Removes a request comment by Comment ID, under the request with the Request ID.
- Delete a Response Comment Removes a comment by Comment ID from the saved response with the Response ID.
- Delete a Spec Deletes an API spec from your workspace.
- Delete a Spec File Deletes one file from an API spec by File Path.
- Delete a Workspace Deletes a workspace once Confirm is turned on.
- Delete a Workspace Update Removes an update post by its Update ID from a workspace.
- Delete an API Deletes an API definition from Postman.
- Delete an API Version Deletes the release that matches a Version ID from the version list of an API.
- Delete an Environment Deletes a named environment, the variable set of a workspace.
- Duplicate a Collection Copies a collection into a target Workspace. Use Suffix to tell the copy apart from the original.
- Fork a Collection Forks a collection into a target Workspace. Use Label to name the fork.
- Fork an Environment Makes a fork of an environment in a Workspace. Use Fork Name to title the fork.
- Generate a Collection from a Spec Builds a collection out of an API spec under a Name. Use Folder Strategy, Indent Character and Include Deprecated to shape it. It returns a Task Id and Url for following the run.
- Generate a Spec from a Collection Writes an API spec out of a collection from a Name, using Type and Format to set the spec style. Follow the run with its Task Id and Url.
- Get a Collection Downloads a whole collection: Info, Item, Auth, Event and Variable. Use Model to switch the response format and Access Key to read a shared collection.
- Get a Collection Folder Pulls one folder by Folder ID, returning its Name, Description and Owner. Turn on Populate to include what is inside.
- Get a Collection Merge Status Polls a merge task by Task ID and reports its Status.
- Get a Collection Request Looks up one request by Request ID, returning its Name, Owner and Last Revision. Turn on Populate for more detail.
- Get a Collection Response Fetches the saved example response behind a Response ID, with the Request it belongs to, plus its Name and Owner.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Contentful and Postman integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Contentful and Postman.
References
List of sources used to gather information about the Contentful and Postman integration.
- Contentful and Postman integration source code, module specs and credentials implementation.
- Our Contentful and Postman integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Contentful and Postman, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Contentful integration information
- Postman integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Contentful and Postman integration page documentation. Used sources, the role of AI, and how the team validates the result.