Alchemy and Rootly Integration

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

Connect Alchemy 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 Alchemy and Rootly

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

  • Alchemy

    • Developer Tools
    • 1 trigger
    • 113 searches
    • 13 actions

    Blockchain data and node APIs: balances, NFTs, prices, transfers, webhooks and JSON-RPC.[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 Alchemy to Rootly

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

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

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

Alchemy triggersRootly actions

Alchemy modules

  • Watch Events (Instant) Starts the workflow each time Alchemy sends an event to the webhook, with its Webhook ID, Event ID, Type, Network and Activity.
  • Add or Remove Webhook Addresses Edits the watched addresses of a webhook in place. Use Addresses to Add to start watching more addresses and Addresses to Remove to stop watching some.
  • Call a Contract Runs a read-only call against a smart contract at the To address with the encoded Data, and reads the Result without sending a transaction. Choose a Block to run it against past state.
  • Call a JSON-RPC Method Sends any JSON-RPC Method of the chosen chain with its Params, for calls that have no dedicated module. Set Custom Network to reach a chain missing from the list.
  • Check a Solana Blockhash Tests whether a Blockhash can still be used in a new transaction, at the chosen Commitment.
  • Check If a Contract Is Spam Asks Alchemy whether the contract at Contract Address is flagged as spam and returns Is Spam Contract.
  • Create a Webhook Variable Saves a list of addresses or 32-byte hex values under a Variable Name so custom webhook queries can use it.
  • Debug Trace a Block by Hash Traces every transaction of one block by Block Hash, giving one result per transaction. Add a Tracer, and set Only Top Call to skip inner calls.
  • Debug Trace a Block by Number Traces the transactions of the block at Block, one result per transaction. Add a Tracer for the trace format and Limit to bound the list.
  • Debug Trace a Call Simulates a call from From to To and traces its execution without sending it. Add State Overrides to rewrite account state first, and Gas, Gas Price and Value to shape the call.
  • Debug Trace a Transaction Replays a mined transaction by its Transaction Hash and returns the execution trace. Use Timeout to stop a slow trace.
  • Debug Trace Several Calls Runs Bundles of calls one after another on top of a Block and traces each. Set Transaction Index to start in the middle of that block.
  • Delete a Webhook Variable Deletes a custom webhook variable and returns Deleted to confirm.
  • Estimate Gas Works out how much gas a transaction would use without broadcasting it. Use Value to include an amount in wei and Data to include call data.
  • Estimate User Operation Gas Estimates the gas limits for an account abstraction User Operation sent to an Entry Point. Add State Override Set to simulate changed account state.
  • Filter Traces Finds traces that involve From Addresses or To Addresses, between From Block and To Block. Page through them with After and Count, and cap the list with Limit.
  • Get a Balance Reads the native coin balance of an Address, at the latest block or at an earlier Block.
  • Get a Block Fetches a block by number or tag. Turn on Full Transactions to get complete transaction objects instead of hashes.
  • Get a Block by Hash Finds a block via its Block Hash. Turn on Full Transactions to include whole transactions instead of only their hashes.
  • Get a Raw Block Fetches the RLP encoded bytes of a whole block with no decoding applied.
  • Get a Raw Block Header Returns only the RLP encoded header of a block, without its body.
  • Get a Solana Account Reads the stored data of a Solana Account. Set Encoding for the data format and Commitment for how final the state must be.
  • Get a Solana Asset Looks up one Solana digital asset by Asset ID. Turn on Show Collection Metadata to include collection details and Show Fungible Tokens to include fungible tokens.
  • Get a Solana Asset Proof Returns the Merkle proof of the compressed asset with this Asset ID.
  • Get a Solana Balance Reads the SOL balance of an Account at the chosen Commitment level.
  • Get a Solana Block Fetches the block at a Slot. Use Transaction Details to control how much transaction data comes along and Max Supported Transaction Version to allow newer formats.
  • Get a Solana Priority Fee Estimate Suggests a priority fee from a Transaction or from a list of Account Keys. Use Priority Level to ask for one tier, or turn on Include All Priority Fee Levels to get the estimate for every level.
  • Get a Solana Token Account Balance Reads the token amount held in one Token Account, such as a wallet SPL token holding.
  • Get a Solana Token Supply Reads how many units exist in total of the token with this Mint.
  • Get a Solana Transaction Fetches a confirmed transaction by its Signature. Set Max Supported Transaction Version to read newer versioned transactions and Encoding to change how the data is returned.
  • Get a Storage Value Reads the raw value held in one storage Slot of the contract at Address, at a chosen Block.
  • Get a Token Allowance Tells how much of a Token Contract the Spender may still move on behalf of the Owner.
  • Get a Trace Returns the trace at the Trace Indexes position of the transaction with this Transaction Hash.
  • Get a Transaction Looks up a transaction by Transaction Hash and returns its fields.
  • Get a Transaction by Block Index Picks the transaction at position Index inside the block at Block, without needing its hash.
  • Get a Transaction Count Counts the transactions sent from an Address, which is also its next nonce, at an optional Block.
  • Get a Transaction Receipt Fetches the outcome of a mined transaction by Transaction Hash, with status, gas used and logs.
  • Get a User Operation Looks up an account abstraction operation by its User Operation Hash. Restrict the search with From Block and To Block.
  • Get a User Operation Receipt Fetches the receipt of an operation by its User Operation Hash, once it has been included in a block.
  • Get a User Operation Status Checks how far an operation has progressed, using its User Operation Hash.
  • Get an Account Proof Returns the Merkle proof of an Address at a Block, covering each of its Storage Keys.
  • Get Asset Transfers Searches historical transfers for the kinds listed under Categories, such as external or token transfers. Narrow by From Address, To Address and a block range, and turn on Exclude Zero Value to drop empty ones.
  • Get Block Receipts Lists the receipts of all transactions in the block at Block, each with its Status, Gas Used and Logs, up to Limit.
  • Get Historical Token Prices Returns the price history of a token between Start Time and End Time. Set Interval to space the points and turn on With Market Data to add market cap and volume. Name the token with a Symbol, or with a Contract Address and a Network.
  • Get Logs Collects event logs emitted by contracts, filtered by Addresses, Topics and a block range from From Block to To Block, up to Limit.
  • Get NFT Collections by Wallet Lists the NFT collections held by up to 2 wallets across up to 15 networks each. Use Order By and Sort Order to arrange the list, and turn off With Metadata for a smaller, faster answer.
  • Get NFT Contract Metadata Describes an NFT collection by its Contract Address, with Name, Symbol, Token Type and Total Supply.
  • Get NFT Contract Metadata in Bulk Looks up the Name, Symbol and Token Type of many NFT collections in one request, for many contract addresses at once.
  • Get NFT Contracts for an Owner Lists the collections held by an Owner wallet with their Total Balance and Num Distinct Tokens Owned. Add Include Filters or Exclude Filters to trim the list and Order By to sort it.
  • Get NFT Floor Prices Checks the lowest listing price of a collection on marketplaces such as Open Sea and Looks Rare. Identify it with a Contract Address or a Collection Slug.

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

Automate Alchemy and Rootly on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Alchemy and Rootly.

How do I connect Alchemy and Rootly?

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

Example: when the "Watch Events (Instant)" trigger in Alchemy fires, WEXTL can "Acknowledge an Alert" in Rootly. Alchemy has 1 trigger (including Watch Events (Instant)). 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 Alchemy trigger actions in Rootly, and Rootly in Alchemy?

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

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

Does Alchemy integrate with Rootly in real time?

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

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

References

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

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

Explore Alchemy and Rootly, or get started