Alchemy and Bitbucket Integration

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

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

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

  • Bitbucket

    • Developer Tools
    • 5 triggers
    • 65 searches
    • 50 actions

    Bitbucket Cloud REST 2.0 with repositories, pull requests, pipelines, commits and webhooks.[6]

How to connect Alchemy to Bitbucket

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

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

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

Bitbucket modules

  • Approve a Commit Marks a commit as approved by the connected account. The result reports the participant Role and State, plus the Participated On time.
  • Approve a Pull Request Signs off on a pull request from List Pull Requests as the connected account. The output shows whether Approved is set for that participant.
  • Compare Commits Builds a diff from a Spec holding one commit hash, compared with its first parent, or two commits separated by two dots. Use Path to narrow it to one file and Ignore Whitespace to skip whitespace edits.
  • Create a Branch Creates a branch from the commit hash or branch name given as the Hash of Target. Use Branch Name without the refs/heads prefix. Output includes the Merge Strategies and Default Merge Strategy of the new branch.
  • Create a Build Status Reports a build result against a commit. Set State to FAILED, INPROGRESS, STOPPED or SUCCESSFUL, give each status its own Key and add a Url that links back to the build system.
  • Create a Commit Comment Leaves a comment against a commit, with Content as its text. The new comment returns with its Id, Created On time and User.
  • Create a Commit from Files Commits files straight into a repository from File Parts, each part keyed by its repository path. Use Message and Author to describe the commit and Branch to say where it lands. The new commit returns with its Hash.
  • Create a Pipeline Schedule Sets up a recurring pipeline run from a Target and a Cron Pattern, which uses seven fields for second precision. Set Enabled to switch the schedule on.
  • Create a Project Sets up a project in a workspace with a Name and Key. Use Description to explain its purpose and turn on Is Private to make it private.
  • Create a Pull Request Opens a pull request that merges one branch into another, using Title and Summary for the text. Turn on Close Source Branch to close the source branch after merging, and list Reviewers to request their review.
  • Create a Pull Request Comment Writes a comment onto a pull request from List Pull Requests, using Content for the text. Output includes its Id, Parent and Resolution.
  • Create a Pull Request Task Adds a to-do item to a pull request. Use Task Raw Content for the wording and turn on Pending to mark it pending.
  • Create a Repository Sets up a repository under a workspace with a Repository Slug. Add a Name, Description or Language, and turn on Is Private, Has Issues or Has Wiki as needed.
  • Create a Repository Variable Saves a pipeline variable against a repository, defined by Key and Value. Turn on Secured to keep its value out of the logs and the REST API.
  • Create a Tag Marks a commit with a tag. Use Name to label the tag, Target to choose the commit and Message to annotate it.
  • Create an Environment Variable Defines a variable inside a deployment environment from List Environments, with a Key and a Value. Turn on Secured to keep the value out of the logs and the REST API.
  • Decline a Pull Request Closes a pull request from List Pull Requests without merging it. The returned pull request shows its State and the Reason it was declined.
  • Delete a Branch Deletes a Bitbucket branch by name from a repository.
  • Delete a Commit Comment Removes a comment attached to a repository commit.
  • Delete a Download Artifact Deletes a file stored in the downloads section of a repository.
  • Delete a Pipeline Schedule Deletes a recurring pipeline schedule from a repository.
  • Delete a Project Deletes a workspace project by its key.
  • Delete a Pull Request Comment Removes a comment written on a pull request.
  • Delete a Pull Request Task Deletes a task listed on a pull request review.
  • Delete a Repository Deletes a whole repository. Use Redirect To to point the old address at a new location.
  • Delete a Repository Variable Removes a pipeline variable stored on a repository.
  • Delete a Tag Removes a git tag in a Bitbucket repository, located by its Workspace, Repository and Tag.
  • Delete an Environment Variable Removes a variable defined for a deployment environment.
  • Fork a Repository Makes a fork of a repository under a new Name. Use Description, Is Private and Fork Policy to adjust the copy. The fork returns with its Full Name and Uuid.
  • Get a Branch Reads one branch, using a Branch from List Branches. Output includes its Name, Target and Default Merge Strategy.
  • Get a Build Status Finds the build status on a commit that matches the Build Status Key from List Commit Statuses. Output includes State, Url and Description.
  • Get a Commit Loads a commit for the Commit from List Commits, with its Hash, Author, Message and Summary.
  • Get a Commit Comment Reads one comment left on a commit, using a Comment from List Commit Comments. Output includes its Content, User and Deleted setting.
  • Get a Commit Diffstat Summarises the files touched by a Spec, giving Lines Added and Lines Removed for each. Use Limit to set roughly how many entries to return.
  • Get a Commit Patch Produces a patch for a Spec that holds one commit or two commits separated by two dots. Output includes Body with the patch text.
  • Get a Download Artifact Retrieves a stored download using the Download from List Downloads. Output includes the File, its Filename, Size and Content Type.
  • Get a File or Directory Reads whatever sits at a Path in a repository, for the Commit from List Commits. Use Max Depth to control how far a directory listing descends.
  • Get a Merge Base Finds the shared ancestor of two commits given as revspec. The ancestor is returned with its Hash, Date, Author and Message.
  • Get a Pipeline Loads a run from List Pipelines, including its Build Number, State, Trigger and Build Seconds Used.
  • Get a Pipeline Config Shows whether pipelines are Enabled for a repository, along with the Repository it belongs to.
  • Get a Pipeline Schedule Reads a schedule from List Pipeline Schedules. Output includes its Cron Pattern, Target and Enabled setting.
  • Get a Pipeline Step Examines one step of a pipeline from List Pipeline Steps. Output includes its Image, Setup Commands, Script Commands, Started On and Completed On.
  • Get a Pipeline Step Log Fetches the log output of one pipeline step from List Pipeline Steps. Output includes Body with the log text.
  • Get a Project Reads one project of a workspace, with its Key, Name, Description and Is Private setting.
  • Get a Pull Request Opens a pull request from List Pull Requests for reading, with its Title, State, Author, Source and Destination.
  • Get a Pull Request Comment Reads a single comment on a pull request, using a Comment from List Pull Request Comments. Output includes Content, Inline placement and Resolution.
  • Get a Pull Request Diff Fetches the unified diff of a pull request. Output includes Body, the whole diff.
  • Get a Pull Request Diffstat Counts the changes on a pull request file by file, with Status, Lines Added and Lines Removed. Use Limit to set roughly how many files to return.
  • Get a Pull Request Merge Task Status Checks progress of an asynchronous merge using a Task from List Pull Request Tasks. Output includes Task Status and Merge Result.
  • Get a Pull Request Patch Gets a pull request as a patch. Output includes Body with the patch text.

Explore alternative integrations

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

Automate Alchemy and Bitbucket on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Alchemy and Bitbucket.

How do I connect Alchemy and Bitbucket?

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

Example: when the "Watch Events (Instant)" trigger in Alchemy fires, WEXTL can "Approve a Commit" in Bitbucket. Alchemy has 1 trigger (including Watch Events (Instant)). Bitbucket has 115 actions (including Approve a Commit, Approve a Pull Request, and Compare Commits). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Alchemy and Bitbucket, or get started