Memberstack and Rootly Integration

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

Keep Memberstack and Rootly matched by integrating their events and actions. When developer tools events happen in Memberstack, update the Rootly 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 Memberstack and Rootly

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

  • Memberstack

    • Developer Tools
    • 2 triggers
    • 7 searches
    • 10 actions

    Membership platform for authentication, gated content, plans, and member records.[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 Memberstack to Rootly

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

How does the integration between Memberstack and Rootly work in WEXTL?

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

Memberstack triggersRootly actions

Memberstack modules

  • Add a Free Plan Gives a member a free plan whose Plan ID starts with pln_. Map a Member ID to reach any member, not just the 100 newest.
  • Count Data Records Counts how many records in a data table match your filter. Use Where to narrow the count with conditions written as a JSON object or array.
  • Create a Data Record Adds a row to a data table from the key-value pairs of Data. Use Member ID to give the record a member owner, or leave it empty for none. The response gives its ID, Created at and Internal order.
  • Create a Member Registers a member from an Email, plus a Password unless the app uses passwordless login. Use Plans to attach free plans and Custom fields to fill in profile data. The response includes the new ID and Plan connections.
  • Delete a Data Record Deletes a single record from a data table, and the deletion cannot be undone. The deleted record is returned with its Data and Created at.
  • Delete a Member Deletes a member from the app, which cannot be undone. Two Stripe switches default to No, and turning them on also deletes the Stripe customer and cancels their subscriptions.
  • Get a Data Record Fetches one record from a data table by its Record ID, with its Data along with Created at and Updated at.
  • Get a Data Table Fetches the definition of one data table by its key, such as products, or by its ID. You get the Fields plus the Create rule, Read rule, Update rule and Delete rule.
  • Get a Member Looks up a member by member ID (mem_…) or by email address. A member that does not exist gives null data. Turn on Include teams to add team memberships.
  • List Data Tables Lists the data tables of your Memberstack app, capped by Limit. Each table carries its Key, Name and Fields.
  • List Members Returns the members of your app, up to Limit. Use Order to switch between ASC and DESC, and turn on Include JSON to add the json field of each member.
  • Make an API Call Sends a free-form request to the Memberstack REST API, signed with your saved credential.
  • Query Data Records Finds records in a data table that match the conditions of Where, such as equals, contains or startsWith. Use either Select to return only some fields or Include to bring related records or counts, since sending both returns an error.
  • Remove a Free Plan Revokes a free plan of a member. Paid plans are not changed here.
  • Update a Data Record Changes only the fields you send with Data on an existing record. Send at least one key. The result includes the refreshed Updated at.
  • Update a Member Gives a member new values for Email, Custom fields, Metadata, Verified or Profile image. Anything left empty keeps its current value. Use JSON to replace the entire JSON object.
  • Verify a Member Token Checks whether a member Token is valid and gives the result as Data. An invalid or expired token fails with INVALID_TOKEN.
  • Watch New Data Records Checks a data table on your schedule and starts the workflow once for every record added since the previous check. Use Limit to cap one poll, which returns at most 100 rows.
  • Watch New Members Checks on your schedule for newly added members and runs the workflow once per member. Use Limit to cap how many members the first poll returns.

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

Automate Memberstack and Rootly on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Memberstack and Rootly.

How do I connect Memberstack and Rootly?

Connect your Memberstack 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 Memberstack and Rootly?

Example: when the "Watch New Data Records" trigger in Memberstack fires, WEXTL can "Acknowledge an Alert" in Rootly. Memberstack has 2 triggers (including Watch New Data Records and Watch New Members). 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 Memberstack trigger actions in Rootly, and Rootly in Memberstack?

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 Memberstack and Rootly?

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

Does Memberstack integrate with Rootly in real time?

Yes. Trigger-based automations start the moment Memberstack (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 Memberstack + 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 Memberstack with Rootly?

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

References

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

  1. Memberstack and Rootly integration source code, module specs and credentials implementation.
  2. Our Memberstack and Rootly integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Memberstack 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. Memberstack 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 Memberstack and Rootly integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Memberstack and Rootly, or get started