Alchemy and Lokalise Integration

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

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

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

  • Lokalise

    • Developer Tools
    • 1 trigger
    • 53 searches
    • 63 actions

    Translation management with projects, keys, translations, files, tasks, orders, contributors and webhooks.[6]

How to connect Alchemy to Lokalise

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

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

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

Lokalise modules

  • Add Members to a Group Adds a list of Users to a team group in Lokalise and shows the updated group with its Projects.
  • Add Projects to a Group Gives a team group access to more projects through its Projects list. Returns the group with its Permissions.
  • Create a Branch Creates a branch within a project, with an optional Name. The Branch ID and its creator are returned.
  • Create a Group Sets up a team group. Choose Is Reviewer or Is Admin, pick Role ID and Admin Rights for permissions, and limit languages through Languages Reference and Languages Contributable.
  • Create a Project Creates a Lokalise project from a Name, with its languages listed by Language ISO Code. Pick a Project Type such as Localization Files or Paged Documents, and a Base Lang.
  • Create a Service Token Issues a service token for one project, with Ota as the Service, and returns the Jwt.
  • Create a Snapshot Saves the current state of a project as a snapshot, labeled with an optional Title.
  • Create a Task Creates a translation or review task from a Title, with Languages, Keys, a Due Date and a Source Language. Set the auto close options to finish work automatically.
  • Create a Translation Status Adds a custom translation status for a project, using a Title and a Color.
  • Create a Webhook Registers a webhook in a project that posts the chosen Events to a URL. Use Branch to watch one branch and Event Lang Map to limit events to languages. Returns the Secret.
  • Create an Order Places a PAID translation order with a Provider Slug and Translation Tier for the Keys of a project. Fill in a Briefing, Source Language and Target Language ISO Codes, or turn on Dry Run to get a quote only.
  • Create Billing Details Saves the invoicing details of a team from a Billing Email, Country Code and Zip. Add Address1, Address2, City, Company or Vatnumber for the full address.
  • Create Contributors Invites people by Email, giving each the Languages they may work on. Created contributors show their admin and reviewer rights.
  • Create Glossary Terms Adds terms to a project glossary with a Description and the flags Case Sensitive, Translatable and Forbidden. Each created term is returned with its Translations.
  • Create Key Comments Posts Comments on a translation key, optionally on a Branch. The saved comments show who added them and when.
  • Create Keys Creates translation keys, each with a Key Name and Platforms. Turn on Use Automations to run project automations on them, and read each Filenames value in the result.
  • Create Languages Adds target languages to a project through a Language ISO Code each. The result shows the Lang Name and Plural Forms of every language.
  • Create Screenshots Uploads screenshots to a project as base64 Data, with Title, Description and linked Key IDs. Each result includes the screenshot URL.
  • Delete a Branch Deletes a branch within a project. The reply shows Project ID and Branch ID.
  • Delete a Card Removes a stored payment card from the team.
  • Delete a Comment Deletes one comment left on a key. Pass a Branch to reach a comment on a branch.
  • Delete a Contributor Revokes the access of one contributor to a project.
  • Delete a File Deletes an uploaded file from a project, and reports the File ID with Deleted.
  • Delete a Group Deletes a user group of a team, returning Deleted, Team ID and Group ID.
  • Delete a Key Removes a single translation key and reports Deleted.
  • Delete a Language Removes a language from translation work in a project, giving back its Lang ID.
  • Delete a Project Deletes a whole project along with ALL the keys inside it, and reports Deleted with its Project ID.
  • Delete a Screenshot Deletes a screenshot, returning Deleted and the Screenshot ID.
  • Delete a Snapshot Removes a saved copy of a project, giving back its Snapshot ID.
  • Delete a Task Removes a translation task from the project.
  • Delete a Team User Removes a member from a team, giving back Team ID and User ID.
  • Delete a Translation Status Deletes a custom translation status, returning its Status ID.
  • Delete a Webhook Deletes a webhook and returns Deleted with its Webhook ID.
  • Delete All Contributors Removes ALL contributors from a project in a background job, once Confirm is set. Returns a Job ID to follow it.
  • Delete Glossary Terms Removes all the chosen terms from the glossary of a project.
  • Delete Multiple Keys Removes all the chosen translation keys in one request, and the result counts Keys Removed and Keys Locked.
  • Delete Project Content Clears ALL keys and translations of a project once Confirm is set.
  • Download Files Exports project translations in a chosen Format as a zip. Use Filter Langs to limit languages, Directory Prefix and Bundle Structure to shape paths, and receive a Bundle URL.
  • Download Files Async Queues an export of project translations in a Format and returns a Process ID to poll.
  • Get a Branch Looks up a branch of a project and shows who it was Created By and when.
  • Get a Card Shows a stored payment card by Brand and Last4.
  • Get a Comment Fetches one comment on a key with its Comment text and who it was Added By. Pass a Branch to read from a branch.
  • Get a Contributor Returns a project contributor with Email and Fullname, plus whether they are an admin or reviewer through Is Admin and Is Reviewer.
  • Get a Contributor Deletion Job Checks a deletion job by Job ID, showing its State and how far it got through Total, Processed and Deleted.
  • Get a Glossary Term Retrieves a glossary entry with its Description and Translations, plus Case Sensitive, Translatable and Forbidden settings.
  • Get a Group Shows a team group with its Name, Permissions and the Projects it can reach.
  • Get a Key Retrieves a translation key with its Key Name, Description and Platforms. Turn on Include Ai Scoring to add AI quality scores, or Disable References to skip reference resolution.
  • Get a Key Language Segment Fetches a segment of a key in a single language, using Language ISO Code and Segment Number. Returns the Value and who Modified By.
  • Get a Language Gets a project language with its Lang Name, Is Rtl flag and Plural Forms.
  • Get a Process Checks a background process of a project, showing its Type, Status and Message.

Explore alternative integrations

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

Automate Alchemy and Lokalise on WEXTL®

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

Cancel anytime.

Frequently asked questions

Common questions about connecting Alchemy and Lokalise.

How do I connect Alchemy and Lokalise?

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

Example: when the "Watch Events (Instant)" trigger in Alchemy fires, WEXTL can "Add Members to a Group" in Lokalise. Alchemy has 1 trigger (including Watch Events (Instant)). Lokalise has 116 actions (including Add Members to a Group, Add Projects to a Group, and Create a Branch). Add filters and transforms between steps when you need them.[1]

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

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

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

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

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

Explore Alchemy and Lokalise, or get started