Contentful and Rootly Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Connect Contentful and Rootly to automate developer tools workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Contentful and Rootly
Detailed info you need to know about Contentful and Rootly 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]
Rootly

Incident management and on-call platform for detecting, responding to, and learning from incidents.[6]
How to connect Contentful to Rootly
Set up your Contentful and Rootly integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Contentful and Rootly
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 Rootly 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 Rootly. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Contentful and Rootly work in WEXTL?
WEXTL exposes actions and triggers for Contentful and Rootly 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 triggersRootly 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.
Rootly modules
- Acknowledge an Alert Marks an alert as acknowledged. Use Actor Email to record a specific user as the one who did it, when your organization has actor attribution turned on.
- Add a Note to an Alert Writes a Note on the activity feed of an alert, credited to the chosen User.
- Add a Timeline Event to an Incident Writes an Event on the timeline of an incident. Set Visibility to control who can read it.
- Add Subscribers to an Incident Subscribes the chosen Users to updates on an incident. Turn on Skip Users Without Access to a Private Incident to leave out anyone who cannot see it.
- Assign a Role to a User on an Incident Gives a user an Incident Role on a single incident and returns the updated incident.
- Attach Alerts to an Incident Links existing alerts to an incident by their Alert IDs and returns the Incident ID with its Alerts.
- Cancel an Incident Cancels an incident, with an optional Cancellation Message giving the reason.
- Create a Cause Adds a cause that incidents and retrospectives can be traced to. Give it a Name, and a Public Name and Public Description for status pages.
- Create a Functionality Adds a functionality, a capability of your product, from its Name. Link Owner Teams, Owner Users, Environments and Services to show who is behind it.
- Create a Heartbeat Sets up a heartbeat that alerts when pings stop. Define the Interval with its Interval Unit, an Alert Summary, and who to page through Notification Target Type and Notification Target ID.
- Create a Pulse Records a pulse from its Summary. Link Services and Environments, and use Labels, References and Data for extra detail.
- Create a Schedule Creates an on-call schedule from a Name and an Owner. Use Time Zone, Owner Teams and Send Shift Reports to adjust it.
- Create a Service Registers a service from its Name. Link Owner Teams, Owner Users, Related Services and an Alert Urgency to place it in the rest of your setup.
- Create a Severity Adds a severity level from a Name. Use Severity Level to rank how serious it is, and Color and Notify Emails to customise it.
- Create a Status Page Builds a status page titled by Title. Turn Public and Enabled on or off, style it with Header Color and Footer Color, and choose Services and Functionalities to cover.
- Create a Status Page Announcement Posts an announcement to a status page, from its Title and Body. Turn on Notify Subscribers to alert followers.
- Create a Sub-Status Adds a sub-status under a Parent Status, from a Name. Use Position to order it among its siblings.
- Create a Team Forms a responder team called Name. Add Members and Admins, a Color and an Alert Urgency, and switch on Alerts by Email.
- Create an Action Item Adds a follow-up task to an incident from its Summary. Set a Kind, Priority and Due Date, and name an Assignee or Assigned Teams to own it.
- Create an Alert Raises an alert from a Summary. Link Services, Teams and Environments, choose an Alert Urgency, and page someone with Notification Target Type and Notification Target ID.
- Create an Alert Urgency Defines an urgency level from a Name and Description. Use Retrigger After to set how long Rootly waits before alerting again on an unacknowledged alert.
- Create an Environment Adds an environment such as production, from its Name. Use Notify Emails, Color and External ID to describe and link it.
- Create an Escalation Policy Builds an escalation policy from a Name. Use Repeat Count to loop it several times, and Teams and Services to attach it.
- Create an Incident Declares an incident. Add a Title, Severity and Summary, link Services, Environments and Incident Types, and set Private to restrict who can see it.
- Create an Incident Role Defines a role people can hold during incidents, from a Name. Turn on Optional, Enabled or Allow Several Users to shape it.
- Create an Incident Type Adds a type for classifying incidents, from a Name. Use Color and Notify Emails to customise it.
- Create an Override Shift Puts a User on call for a window on a schedule, between Starts At and Ends At in UTC.
- Delete a Cause Deletes a cause used to classify incidents.
- Delete a Functionality Removes a functionality, a product capability, from the catalog.
- Delete a Heartbeat Deletes a heartbeat monitor that expected regular pings.
- Delete a Schedule Removes an on-call schedule from Rootly.
- Delete a Service Deletes the chosen service from the Rootly account.
- Delete a Severity Removes a severity level used for incidents.
- Delete a Status Page Deletes a customer-facing status page from Rootly.
- Delete a Status Page Announcement Removes an announcement posted on a status page.
- Delete a Status Page Event Deletes an incident update that was posted to a status page.
- Delete a Sub-Status Deletes a sub-status that sits under a parent status.
- Delete a Team Removes a team from Rootly once Confirm is turned on, because it cannot be undone.
- Delete an Action Item Deletes an action item from Rootly. Turn on Confirm to go ahead, because it cannot be undone.
- Delete an Alert Urgency Removes an urgency level that alerts can carry.
- Delete an Environment Removes an environment from your Rootly catalog.
- Delete an Escalation Policy Deletes a paging policy from Rootly.
- Delete an Incident Removes an incident and its record from Rootly.
- Delete an Incident Role Removes a role that responders can take during incidents.
- Delete an Incident Timeline Event Deletes one chronology entry from the timeline of an incident.
- Delete an Incident Type Removes a type used to classify incidents.
- Delete an Override Shift Deletes a temporary on-call override from a schedule.
- Detach an Incident from Its Parent Separates a child incident from the parent incident it was grouped under.
- Escalate an Alert Raises an alert to a higher level of an escalation policy. Name the Escalation Policy and Escalation Policy Level, or leave the level empty for the next one.
- Get a Cause Looks up a cause with its Slug, Public Name and Position.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Contentful and Rootly 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 Rootly.
References
List of sources used to gather information about the Contentful and Rootly integration.
- Contentful and Rootly integration source code, module specs and credentials implementation.
- Our Contentful and Rootly integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Contentful and Rootly, 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
- Rootly integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Contentful and Rootly integration page documentation. Used sources, the role of AI, and how the team validates the result.