Microsoft OneNote and Rootly Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build developer tools workflows between Microsoft OneNote and Rootly on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Microsoft OneNote and Rootly

Detailed info you need to know about Microsoft OneNote and Rootly integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Microsoft OneNote

    • Developer Tools
    • 4 triggers
    • 8 searches
    • 9 actions

    Create and manage OneNote notebooks, sections, and pages from your workflows.[5]

  • Rootly

    • Developer Tools
    • 1 trigger
    • 63 searches
    • 86 actions

    Incident management and on-call platform for detecting, responding to, and learning from incidents.[6]

How to connect Microsoft OneNote to Rootly

Set up your Microsoft OneNote and Rootly integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Microsoft OneNote and Rootly work in WEXTL?

WEXTL exposes actions and triggers for Microsoft OneNote 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.

Microsoft OneNote triggersRootly actions

Microsoft OneNote modules

  • Copy a OneNote Page Places a duplicate of a OneNote page into another section of a group, using Group ID.
  • Copy a Section to Group Duplicates a section beneath a section group of the destination notebook. Use Rename As to give the copy its own name. Set Group ID only for Microsoft 365 groups.
  • Copy a Section to Notebook Sends a copy of a section to another notebook and returns the new section with its Display name and Pages URL. Use Destination Notebook ID to name the target, Rename As to name the copy, and Group ID when copying to a Microsoft 365 group.
  • Create a Note Book Adds a private notebook to OneNote. Use Display Name to title it. Output includes the ID, Sections URL and User role of the new notebook.
  • Create a Page Writes a new page into a section, built from your HTML Page Content. Output includes the Title and Content URL.
  • Create a Section Group Makes a new section group under an existing one. Use Section ID for the parent and Display Name to label it. The Pages URL of the new group is in the output.
  • Delete a OneNote Page Deletes a OneNote page and its content from your notebooks, found by OneNote Page ID.
  • List Note Books Returns notebooks as separate items with Display name, Is shared and User role. Use Limit to return only the first few.
  • List Note Pages Gathers pages one item at a time, with Title, Created date time and Content URL for each. Use Limit to cap the number of pages returned.
  • List Note Sections Fetches sections with Display name, Is default and Pages URL on each. Use Limit to trim the result to a set count.
  • List Note Sections Groups Collects section groups with Display name, Sections URL and Section groups URL on each. Apply Limit to return only part of them.
  • List Recent Note Books Shows recently opened notebooks, with Last accessed time and Source service for each. Turn on Include Personal Notebooks to add private ones, and set Limit for a shorter list.
  • Make an API Call Makes an authorized free-form request to the Microsoft OneNote REST API with your saved credential.
  • Retrieve a Note Book Loads one notebook by Notebook ID. Output includes Is shared, User role and a Sections URL for reaching its sections.
  • Retrieve a OneNote Page Reads one page by OneNote Page ID. Output includes its Title, Level, Order and the page Content.
  • Retrieve a Section Loads a section by Section ID and returns its Display name, Created by details and Pages URL.
  • Update a OneNote Page Edits the HTML of an existing page. Each of the OneNote Page Items pairs an Action with a Target, and may add Content with a Position before or after the target.
  • Watch Note Pages Runs on a polling schedule and emits each page added since the previous check, with its Title and Content URL. Use Limit to set the most pages handled per run.
  • Watch Notebooks Checks on a schedule for notebooks created since the last run and starts the workflow once for each. Use Limit to bound the notebooks handled in one run.
  • Watch Section Groups Looks for section groups added since the last scheduled check and triggers once per group. Set Limit to restrict how many are processed in one cycle.
  • Watch Sections On each scheduled poll, picks up sections created since the previous one and emits them one by one with their Is default flag. A cycle stops at the Limit.

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 Microsoft OneNote and Rootly integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Microsoft OneNote and Rootly on WEXTL®

Claim your 3-day trial to build Microsoft OneNote with Rootly integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Microsoft OneNote and Rootly.

How do I connect Microsoft OneNote and Rootly?

Connect your Microsoft OneNote and Rootly accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Microsoft OneNote and Rootly?

Example: when the "Watch Note Pages" trigger in Microsoft OneNote fires, WEXTL can "Acknowledge an Alert" in Rootly. Microsoft OneNote has 4 triggers (including Watch Note Pages, Watch Notebooks, and Watch Section Groups). Rootly has 149 actions (including Acknowledge an Alert, Add a Note to an Alert, and Add a Timeline Event to an Incident). Add filters and transforms between steps when you need them.[1]

Can Microsoft OneNote trigger actions in Rootly, and Rootly in Microsoft OneNote?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Microsoft OneNote and Rootly?

No. Microsoft OneNote-to-Rootly automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Microsoft OneNote integrate with Rootly in real time?

Yes. Trigger-based automations start the moment Microsoft OneNote (or Rootly) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Microsoft OneNote + Rootly integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Microsoft OneNote with Rootly?

You can build your Microsoft OneNote + Rootly automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Microsoft OneNote and Rootly integration.

  1. Microsoft OneNote and Rootly integration source code, module specs and credentials implementation.
  2. Our Microsoft OneNote and Rootly integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Microsoft OneNote and Rootly, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Microsoft OneNote integration information
  6. Rootly integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Microsoft OneNote and Rootly integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Microsoft OneNote and Rootly, or get started