Alchemy and PagerDuty Integration

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

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

Detailed info you need to know about Alchemy and PagerDuty 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]

  • PagerDuty

    • Developer Tools
    • 2 triggers
    • 69 searches
    • 79 actions

    Incident management and on-call with services, schedules, escalation policies and incidents with webhook subscriptions.[6]

How to connect Alchemy to PagerDuty

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

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

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

PagerDuty modules

  • Add a User to a Team Puts a user on a team, optionally with a given Role.
  • Add an Escalation Policy to a Team Attaches an existing escalation policy to a team and links the two.
  • Add Notification Subscribers Signs up people or teams as Subscribers for the status updates on one incident. The response includes the Result for each subscriber.
  • Assign Tags Adds and removes tags on an escalation policy, incident, service, team or user in one call. Use Add Tags for new or existing tags and Remove Tags to detach tags the entity already has.
  • Cancel Responder Requests for an Incident Cancels responder requests on an incident for the chosen Responder Request Targets, made by the Requester.
  • Change the Impact of an Incident on a Business Service Sets whether an incident impacts a business service, through Relation (Impacted or Not Impacted). The output returns the Relation.
  • Convert the Event Rules of a Service into Event Orchestration Rules Converts event rules from a service into event orchestration rules. The output reports a Convert Status and where they were Converted To.
  • Create a Change Event Records a change in PagerDuty from a Summary and a Source. Use Timestamp to set when the change occurred (it defaults to now) and Custom Details to attach more information.
  • Create a Maintenance Window Stops the listed Services from creating incidents from a Start Time until an End Time, when they start creating incidents again.
  • Create a New Integration Creates an integration on a service from a Type or a Vendor. For email integrations, add Email Filters and choose Email Incident Creation to control how messages open incidents.
  • Create a Note on an Incident Posts a note on an incident. Output includes the Channel and Created At of the note.
  • Create a Responder Request for an Incident Asks users or escalation policies to respond to an incident, sending a Message from the Requester.
  • Create a Schedule Builds an on-call rotation in a Time Zone from one or more Schedule Layers. Give it a Name and Description, and allow Overflow to let shifts run past the end of the range.
  • Create a Service Adds a service that incidents attach to, tied to an Escalation Policy. Add Auto Resolve Timeout, Acknowledgement Timeout, Alert Grouping or Support Hours to shape how incidents behave.
  • Create a Status Update on an Incident Posts a Message as a status update on an incident. Fill Subject and HTML Message to send a custom HTML email update.
  • Create a Tag Makes a tag from a Label. Attach it to entities with Assign Tags.
  • Create a Team Makes a team in PagerDuty from a Name. Use Description to describe the team and set Default Role to Manager or None.
  • Create a User Adds a user from a Name and Email, with an optional Role, License ID, Job Title, Color and Time Zone for the profile.
  • Create a User Contact Method Gives a user a new way to be reached, such as an email address or phone number. Fill Type, Label and Address, then Country Code if it is a phone.
  • Create a User Handoff Notification Rule Warns a user before an on-call shift changes hands, through a chosen Contact Method Type. Add a Notify Advance in Minutes delay before the rule fires.
  • Create a User Notification Rule Adds a step to how a user is alerted for incidents of a given Urgency. Wait before it fires with Start Delay in Minutes and choose the channel with Contact Method Type.
  • Create a User Status Update Notification Rule Defines how a user receives incident status updates, through a Contact Method Type.
  • Create an Escalation Policy Creates an escalation policy from a Name and ordered Escalation Rules. Use Number of Loops to repeat the policy after the last rule.
  • Create an Event Rule on a Service Creates an event rule on a service that matches incoming events by Conditions and then runs its Actions. Use Position to set its index, Time Frame to restrict when it applies and Disabled to create it switched off.
  • Create an Incident Raises an incident on a Service, under a Title. Rank it with Urgency and Priority, route it by Escalation Policy, and add an Incident Key to avoid duplicates.
  • Create Notification Subscriptions Signs one user up for the Subscribables listed, with a Result returned per entry.
  • Create One or More Overrides Replaces who is on call during specific time ranges on a schedule. Each entry of Overrides names a user and its own start and end. Output lists the Status and Errors of every override.
  • Create Team Notification Subscriptions Subscribes a team to the Subscribables listed. The output gives a Result per subscription.
  • Delete a Note on an Incident Removes a single note attached to an incident in PagerDuty.
  • Delete a Schedule Removes an on-call schedule from PagerDuty, given its Schedule ID.
  • Delete a Service Deletes the whole service with this Service ID from your PagerDuty account.
  • Delete a Tag Deletes the tag label with this ID from the tag list of your PagerDuty account.
  • Delete a Team Removes a team. Use Reassignment Team to move its unresolved incidents to another team.
  • Delete a User Removes a person from PagerDuty by User ID.
  • Delete a User Contact Method Deletes one contact method of a user in PagerDuty, found with User ID and Contact Method ID.
  • Delete a User Handoff Notification Rule Removes a rule that warned a user ahead of on-call shift changes.
  • Delete a User Notification Rule Removes one alert step from the incident notifications of a user.
  • Delete a User Session Ends one login session of a user, found by its Type.
  • Delete a User Status Update Notification Rule Deletes the rule that sent a user incident status updates through one contact method.
  • Delete All User Sessions Signs a user out by ending every session they have, browser and API alike.
  • Delete an Escalation Policy Deletes an escalation policy from your PagerDuty account, using the policy ID.
  • Delete an Event Rule from a Service Deletes one event rule of a service in PagerDuty, picked by the service and rule IDs.
  • Delete an Override Deletes one override from an on-call schedule, found by Schedule ID.
  • Delete or End a Maintenance Window Ends a maintenance window that is running, or deletes a scheduled one that has not started yet.
  • Enable a Webhook Subscription Enables a webhook subscription. The output shows whether it is Active along with its Delivery Method and Events.
  • Get a Change Event Reads one change event with its Summary, Timestamp, Services and Integration.
  • Get a Log Entry Reads a single entry from the PagerDuty log. Use Time Zone to show its times in a chosen zone.
  • Get a Maintenance Window Loads a maintenance window and reports its Sequence Number, Start Time and End Time. Use Include to add more models.
  • Get a Schedule Retrieves a schedule with its Schedule Layers, restricted to the Since to Until range. Add Include Next Oncall For User to see the next shift of one person.
  • Get a Service Pulls up a service with its Name, Description, Auto Resolve Timeout and Acknowledgement Timeout.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Alchemy and PagerDuty integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Alchemy and PagerDuty on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Alchemy and PagerDuty.

How do I connect Alchemy and PagerDuty?

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

Example: when the "Watch Events (Instant)" trigger in Alchemy fires, WEXTL can "Add a User to a Team" in PagerDuty. Alchemy has 1 trigger (including Watch Events (Instant)). PagerDuty has 148 actions (including Add a User to a Team, Add an Escalation Policy to a Team, and Add Notification Subscribers). Add filters and transforms between steps when you need them.[1]

Can Alchemy trigger actions in PagerDuty, and PagerDuty 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 PagerDuty?

No. Alchemy-to-PagerDuty 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 PagerDuty in real time?

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

You can build your Alchemy + PagerDuty 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 PagerDuty integration.

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

Explore Alchemy and PagerDuty, or get started