Skip to content
Docs

Integrations

Interplay’s integration library is the reason a workflow that would normally be weeks of connector code becomes an afternoon on a canvas. The palette ships 600+ prebuilt nodes, and anything missing can be added from a registry, from npm, or generated from a description.

What categories of integration are included?

Section titled “What categories of integration are included?”
Category Examples of what it covers
GenAI & agents LLM provider nodes, agent and tool nodes, MCP client and server support, vector store and search, transforms, conditions, approvals, chat widgets
Enterprise services CRM and business platforms such as Salesforce, enterprise data sources, and product-feed integrations
Cloud AI/ML AWS SageMaker, Google Vertex AI, and general-purpose cloud service endpoints
Data & storage SQL databases (MySQL, PostgreSQL), MongoDB, object storage including Google Cloud Storage, file and directory operations
Messaging & communications Twilio (messaging, voice, and video/room composition), Twitter/X, email and mail streams, push notification services
Commerce commercetools (carts, catalog, customers, orders), Magento, shipping and logistics providers such as Shippo, and address/mail services such as Lob
Voice & conversational Dialogflow, Google Assistant, and Alexa surfaces
Analysis & AI services Sentiment and NLP services, search platforms such as Algolia, computer-vision and image-recognition services, speech-to-text providers
Financial data Market-data and brokerage integrations such as Alpaca (accounts, assets, orders, positions)
Blockchain Ethereum-based content and transaction nodes
Hardware & IoT Device, sensor, and connected-hardware nodes
Core plumbing HTTP in/out, TCP/UDP, MQTT, WebSocket, cron/scheduling, file watch, parsers (JSON, XML, CSV, YAML, HTML), logic, switches, loops, templating, debug

How do you connect to something not in the palette?

Section titled “How do you connect to something not in the palette?”

Four ways, in increasing effort:

  1. Generic HTTP nodes — any REST or GraphQL API can be called without a dedicated node.
  2. AI-generated custom node — describe the integration you need and Interplay generates and deploys the node into your palette.
  3. Registry or npm install — pull an existing published node.
  4. Write it — author a node package, or drop the logic into an inline JavaScript or Python function node.

See Custom Nodes & Extensibility.

Does Interplay support the Model Context Protocol?

Section titled “Does Interplay support the Model Context Protocol?”

Yes, in both directions. Flows can act as MCP clients, connecting to external MCP servers to consume their tools and resources (with connection testing and a server registry), and Interplay can expose capabilities as an MCP server so external agents and IDEs can call into it.

How are integration credentials handled?

Section titled “How are integration credentials handled?”

Credentials live in the platform’s secrets wallet and are referenced by flows rather than embedded in them. Access is granted by role, so a flow author can use a connection without being able to read the secret behind it, and rotating a credential does not require editing flows.

Sources and references

Section titled “Sources and references”