Integrations
Integrations
Use Beam from other platforms: start transfers from their workflows and bring evidence of finished transfers back to them.
Integrations connect Beam to platforms that orchestrate work elsewhere. The platform decides when data should move; Beam moves it between storage endpoints and Room members; the platform gets back what Beam reports about the transfer. Some go the other way: a Studio workflow acts in the platform, for example once a transfer finishes. Payloads never pass through the platform.
| Integration | What it does |
|---|---|
| Bittensor EVM | Beam's relay records receipts of your finished transfers and Room deliveries in Beam's receipts contract on Bittensor EVM mainnet, for every transfer or when a contract of yours asks, at 1 credit each. |
| Chainlink CRE | A smart contract asks for a transfer or a receipt. A Chainlink Runtime Environment workflow starts the transfer through Beam Studio and records a DON-attested Beam report of the finished transfer onchain. |
| Zapier | A Studio workflow runs an action in any app Zapier connects to, through your Zapier MCP server, and can start a Zap when it reaches a step. |