Alchemy and Buildkite Integration

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

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

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

  • Buildkite

    • Developer Tools
    • 2 triggers
    • 70 searches
    • 78 actions

    Continuous integration and delivery platform for running fast, secure pipelines.[6]

How to connect Alchemy to Buildkite

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

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

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

Buildkite modules

  • Add a Cluster Maintainer Makes a user or a team a maintainer of a cluster. Use User or Team ID with the UUID of the user from List Members or of the team from List Teams.
  • Add a Pipeline Webhook Registers a Buildkite webhook on the repository of a pipeline and reports Success with the Pipeline.
  • Add a Team Member Puts a member of the organization into a team under a given Role. Returns the team membership with its Created at time and User.
  • Add a Team Pipeline Links a pipeline to a team at a chosen Access Level. Returns the link with its Created at time.
  • Add a Team Suite Gives a team access to a test suite at a chosen Access Level and returns the link with its Created at time.
  • Archive a Pipeline Archives a pipeline. Unarchive a Pipeline reverses it.
  • Cancel a Build Cancels a build of a pipeline and returns the canceled build with its State and Number.
  • Cancel a Job Cancels one job of a build and returns it with its Type, Name and Step key.
  • Create a Build Triggers a build for a Pipeline at a Commit on a Branch. Add Environment Variables and Meta Data, or Pull Request fields, to shape the run.
  • Create a Build Annotation Writes an annotation with a Body on the page of a build, with a Style and a Context. Turn on Append to extend an existing one.
  • Create a Cluster Creates a cluster with a Name to group agents and queues. Use Emoji and Color to style it, and Maintainers (JSON) to set who maintains it.
  • Create a Cluster Secret Stores a secret Value in a Cluster under a Key that builds use to read it. Add a Policy to attach an access policy.
  • Create a Hosted Queue Sets up a queue on Buildkite hosted agents of the chosen Instance Shape, under a Key, inside a Cluster.
  • Create a Job Annotation Writes an annotation with a Body on one job, with a Style and Priority. Turn on Append to extend an annotation that has the same Context.
  • Create a Pipeline Sets up a pipeline from a Name, a Repository and a Configuration (YAML). Use Default Branch to name the main branch, Tags to label it and Skip Queued Branch Builds to drop queued builds of a branch when a newer build starts.
  • Create a Pipeline Schedule Schedules recurring builds of a pipeline on a Cron Line, labeled with Label. Set Branch and Commit to choose what each scheduled build runs.
  • Create a Pipeline Template Saves a Name and Configuration (YAML) as a template. Turn on Available to offer it when people create pipelines.
  • Create a Pipeline Trigger Gives a pipeline an incoming trigger under a Label. Use Build (JSON) for the build settings, Verification (JSON) for a verification secret, and choose the Type carefully because it cannot be changed after creation.
  • Create a Rule Adds an organization rule of one Type with the Value (JSON) that defines it.
  • Create a Self-Hosted Queue Sets up a queue under a Key for agents you run yourself, inside a Cluster. Turn on Use GitHub App Token to use that token for checkouts.
  • Create a Team Starts a team in the organization under a Name. Turn on Members Can Create Test Suites to let its members create suites.
  • Create a Test Suite Creates a test suite in Test Engine with a Name. Use Team IDs to give teams access to it and Show API Token to get the suite API token back once.
  • Create an Agent Token Issues a token that lets agents register in a Cluster. Use Allowed IP Addresses to limit where it works from, Expires At to set an end date, and Allowed Queue IDs or Allow All Queues for queue access. The token value is shown only once.
  • Create Invitations Invites people by their Emails to join the organization, with a Role and optional Teams.
  • Delete a Build Annotation Removes an annotation from the page of a build in Buildkite.
  • Delete a Cluster Deletes the cluster that groups agents and queues in your organization.
  • Delete a Cluster Secret Removes a secret that was stored for the agents of a cluster.
  • Delete a Job Annotation Deletes an annotation that appears on the page of one job.
  • Delete a Job Log Removes the log output that a job produced.
  • Delete a Pipeline Deletes a pipeline that builds a repository in your Buildkite organization.
  • Delete a Pipeline Schedule Removes a recurring schedule from a pipeline.
  • Delete a Pipeline Template Removes a pipeline template from the templates of your Buildkite organization.
  • Delete a Pipeline Trigger Removes an incoming trigger from a pipeline.
  • Delete a Queue Removes an agent queue, hosted or self-hosted, from its cluster.
  • Delete a Rule Deletes one rule that is set on the organization.
  • Delete a Team Disbands a team defined in your organization.
  • Delete a Test Suite Deletes a test suite recorded in Test Engine for your organization.
  • Delete an Artifact Deletes an artifact that a job uploaded.
  • Disable the GitHub Webhook Processing Stops Buildkite from acting on GitHub webhooks for a pipeline.
  • Enable a Test Turns a test back on after it was muted or skipped. The returned test has its Scope and Name.
  • Enable the GitHub Webhook Processing Lets Buildkite act on GitHub webhooks for a pipeline again.
  • Find a Test Looks up a test in a Test Suite through its Scope and Name, returning matching tests with their ID and Web url.
  • Get a Build Fetches a single build. Turn on Include Jobs to add its jobs, or Include Test Engine Data to add Test Engine data to the output.
  • Get a Cluster Opens a cluster and reports its Default queue id, Name and Description.
  • Get a Cluster Maintainer Pulls one maintainer entry of a cluster, showing whether the Actor type is a user or a team and its Actor id.
  • Get a Cluster Secret Returns the settings of a cluster secret, such as its Key, Description and Policy.
  • Get a Job Loads one job and returns its Type, Name and Step key.
  • Get a Job Log Downloads the output a job logged, with its Content, Size and Header times.
  • Get a Member Opens an organization member and shows their Role and Sso mode.
  • Get a Pipeline Retrieves a pipeline and shows its Name together with its URL and Web url.

Explore alternative integrations

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

Automate Alchemy and Buildkite on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Alchemy and Buildkite.

How do I connect Alchemy and Buildkite?

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

Example: when the "Watch Events (Instant)" trigger in Alchemy fires, WEXTL can "Add a Cluster Maintainer" in Buildkite. Alchemy has 1 trigger (including Watch Events (Instant)). Buildkite has 148 actions (including Add a Cluster Maintainer, Add a Pipeline Webhook, and Add a Team Member). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Alchemy and Buildkite, or get started