Cody AI and Rootly Integration
Wire the ai events of Cody AI straight into the developer tools actions of Rootly on the WEXTL® visual canvas. Handoffs between your ai and developer tools tools stay automatic - drag the nodes, map the fields once, and let AI carry the rest. 3-step setup, no code, no engineering ticket.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Cody AI and Rootly
Detailed info you need to know about Cody AI and Rootly integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Cody AI to Rootly
Set up your Cody AI and Rootly integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Cody AI 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 Cody AI 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 Cody AI and Rootly. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Cody AI and Rootly work in WEXTL?
WEXTL exposes actions and triggers for Cody AI 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.
Rootly triggersCody AI actions
Rootly modules
- Watch Events (Instant) Starts a workflow as soon as Rootly sends a webhook event, the moment it happens.
- 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.
Cody AI modules
- Create a Conversation Starts a Cody conversation with a Name and a Bot. Use Focus Documents to keep its answers to selected documents.
- Create a Document Saves text into a Cody Folder, using a Name and the Content to store. Check Status afterwards to see if processing is done.
- Create a Document from a File Uploads a File to a Folder so Cody can read it. Add a File Name with its extension, since Cody AI reads the type from it. The result is the Key of the uploaded file.
- Create a Document from a Webpage Adds the public page at a URL to the chosen Folder as a document. The Status of the new document shows whether Cody finished reading it.
- Create a Folder Creates a Cody folder that documents can be filed into. Use Name to label it for later lookups with List Folders.
- Delete a Conversation Deletes a conversation from your Cody account.
- Delete a Document Removes a document from your Cody knowledge base.
- Get a Conversation Shows the Name and Bot Id of a conversation. Turn on Include Focus Document IDs to add the documents it is limited to.
- Get a Document Retrieves a document with its Status and Content Url. Run it to find out whether processing has finished.
- Get a Folder Reads one folder and shows its Name along with the Created At time.
- Get a Message Opens one message by Message ID, which Send a Message or List Messages supplies. Shows its Content, whether it was Flagged and its Sources.
- Get an Upload URL Requests a signed address to upload a file yourself, from its File Name and Content Type. You receive the Url to post to and the Key for the file.
- List Bots Lists the bots in your account, each with its Model. Use Keyword to match part of a bot name.
- List Conversations Collects conversation threads, optionally for a single Bot or matching a Keyword. Turn on Include Focus Document IDs to add document IDs to each.
- List Documents Returns stored documents with their Folder Id and Status. Limit the result to one Folder or Conversation, or search names with Keyword.
- List Folders Lists the folders that hold your documents. Use Keyword to search part of the name.
- List Messages Reads message history with each Content and Conversation Id. Set Conversation to follow a single thread.
- Make an API Call Makes an authorized free-form request to the Cody AI REST API with your saved credential.
- Send a Message Writes your Content to a conversation and waits for the answer from the bot. Check Failed Responding to see whether it could reply.
- Send a Message and Get a Stream URL Sends Content to a conversation without waiting for the answer. Read the reply while it is being written through the Stream Url.
- Update a Conversation Renames a conversation with Name, assigns another Bot or sets new Focus Documents. Use Clear Fields to blank values.
- Update a Folder Renames a folder in your Cody knowledge base by changing its Name.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Cody AI 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 Cody AI and Rootly.
References
List of sources used to gather information about the Cody AI and Rootly integration.
- Cody AI and Rootly integration source code, module specs and credentials implementation.
- Our Cody AI and Rootly integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cody AI 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.
- Cody AI integration information
- Rootly integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Cody AI and Rootly integration page documentation. Used sources, the role of AI, and how the team validates the result.

