Alchemy and Currents Integration

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

Build developer tools workflows between Alchemy and Currents 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 Alchemy and Currents

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

  • Currents

    • Developer Tools
    • 1 trigger
    • 23 searches
    • 15 actions

    Track Cypress and Playwright test runs in Currents. Read runs, tests, errors and insights, manage actions and react to run events.[6]

How to connect Alchemy to Currents

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

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

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

Currents modules

  • Cancel a Run Cancels a Currents run before it finishes. Output returns the Run ID, Status and Completion State.
  • Cancel a Run by GitHub CI Cancels the Currents run behind a GitHub Actions workflow, located by Repository Owner, Repository and GitHub Workflow Run ID. The reply holds the Currents Run ID and Cancelled.
  • Create a Jira Issue Opens a Jira issue from a run test named by Test ID, using your Jira Installation ID, Jira Project ID and Jira Issue Type ID. Use Custom Fields to fill Jira fields. It reports the Jira Issue Key and Jira Issue URL.
  • Create an Action Adds a rule with a Name that can quarantine, skip or tag the tests selected by a Matcher, using Actions. Set Expires After to end it on a date. The response lists an Action ID plus its Status.
  • Delete a Project Term Deletes a tag from the filter terms of a project. Only the tag Term Type can be deleted, as other types are rejected. You get the term ID, Name and Count.
  • Delete a Run Removes one Currents run from a project and returns its Run ID.
  • Delete an Action Removes one action, a quarantine, skip or tag rule, in a project. Output shows the Action ID and Archived.
  • Disable an Action Switches an action off. Output includes the Action ID, Name, Description and Status.
  • Enable an Action Switches a disabled action back on, reporting its Action ID, Name and Status.
  • Find a Run Searches a project for one run, matching on CI Build ID, Tag, Branch or Author. Add Status as Passed or Failed to restrict it. You receive the Run ID, Status and Completion State.
  • Generate a Test Signature Works out the stable Signature of a test from its Spec File Path and Test Title in a project.
  • Get a Project Fetches one project and returns its Name, Created At and Default Branch.
  • Get a Run Fetches one test run and returns its Status, Completion State and Duration (ms).
  • Get a Test Failure Context Builds structured failure context for a run, and a narrower one when an Instance ID or Test ID is added. Set Detail to Default, Compact or Summary, and turn on Include Flaky for flaky context.
  • Get a Webhook Looks at one webhook in a project, returning its URL, Label and Events.
  • Get Affected Test Executions Pulls the executions of one test, identified by its Test Signature, within a chosen window. Each shows the Run ID, Title, Executed At and Is Flaky. Add Search to filter and Limit to cap the total.
  • Get an Action Fetches one rule of a project, with its Name, Description, Status and Created At.
  • Get an Instance Reads one spec-file instance by Instance ID, returning its Run ID, Spec and Group ID.
  • Get Project Insights Aggregates run and test results for a project over a date window. Choose a Resolution of 1 day or 1 week, and filter by Tag, Branch, Group or Author.
  • Get Test Results Reads the history of one test by Test Signature, with the Framework and Created At of each result. Apply Limit to hold the output to a count, and Tag, Branch, Author or Group to focus it.
  • Link a Jira Issue Links an existing Jira issue with the Jira Issue Key to the test with a Test ID. Add a Comment, or turn on Include Context In Comment to attach context automatically. Output returns the Currents Issue URL.
  • List Action Test Executions Finds the test executions where an action was applied, over a date range. Each row has a Run ID, Spec File, Title and State. Pass Search or Limit to trim the output.
  • List Actions Retrieves every action in a project, showing each Action ID, Name and Status. Filter by Status of Active, Disabled, Archived or Expired, or run a Search on the name.
  • List Affected Tests Shows tests touched by actions in a time window, with their Signature, Title, Spec File and Last Seen. Narrow with Action Type, Status or Search, and order with Sort Direction.
  • List Errors Collects errors of one project over a given period, each with its Error Message, Spec and Count. Use Group By to group by Message or Signature, and add Tag, Branch or Author to narrow it.
  • List Jira Issue Types Returns the issue types in a Jira Project ID of one Jira Installation ID, each with an ID, Name and Description. Add a Search to match by name, and a Limit to restrict the rows.
  • List Jira Projects Looks up Jira projects reachable through a Jira Installation ID, giving the Key, Name and Description of each. A Search matches a name or key.
  • List Project Runs Pulls runs of a project along with Run ID, Status and Created At. Narrow by Tag, Branch, Author or Environment, combine tags with Tag Operator, and refine through Search or Status.
  • List Project Terms Browses the recorded values of one Term Type for a project, such as tags or branches, each with a Name, Count and Updated At. Use Search for a prefix match and Sort Direction to order them.
  • List Projects Gathers the Currents projects, with a Project ID, Name and Default Branch for each. Set a Limit to stop the list at a set number.
  • List Pull Requests Fetches pull requests of a project that have run activity, flagging Has More Runs on each. Include recent runs through Runs Per Pull Request, or restrict by Tag, Branch, Author, Search or Status.
  • List Spec Files Reads spec files for a project, each with its Signature and Spec. Filter through Tag, Branch or Author, and put a ceiling on the total using Limit.
  • List Tests Searches the tests of a project, returning each Title, Signature and Spec. Narrow the output with Search, Tag, Branch or Author.
  • List Webhooks Shows the webhooks set up on a project, giving each Webhook ID, URL, Label and Events. Add a Limit to stop at a given count.
  • Make an API Call Calls the Currents REST API directly with a free-form request under your saved credential.
  • Reset a Run Resets the failed spec files of a run for another attempt. Add Machine IDs to reset only chosen machines. The Run ID and its Status are returned.
  • Update a Webhook Edits the delivery URL, Events, Label or Headers on a project webhook. Use Events to react to Run Start, Finish, Timeout or Cancel.
  • Update an Action Edits a rule of a project: its Name, Description, Actions, Matcher or Expires After. Results echo the Action ID along with Name and Status.
  • Watch Events Instant trigger that fires when a Currents run starts, ends, times out or is cancelled. Output includes the Event, Run ID, Project ID and Status.

Explore alternative integrations

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

Automate Alchemy and Currents on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Alchemy and Currents.

How do I connect Alchemy and Currents?

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

Example: when the "Watch Events (Instant)" trigger in Alchemy fires, WEXTL can "Cancel a Run" in Currents. Alchemy has 1 trigger (including Watch Events (Instant)). Currents has 38 actions (including Cancel a Run, Cancel a Run by GitHub CI, and Create a Jira Issue). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Alchemy and Currents, or get started