Getting Started
Last updated
Was this helpful?
Last updated
Was this helpful?
Integry is an Integration Platform as a Service (iPaaS) that allows you to embed integrations inside your products in minutes.
You can create and embed integration templates called Flows. Your users can browse these Flows inside your app through our the Embedded Marketplace. You build flows between your app and up to 300+ other apps. Your users get a fully native integration experience within your product. Their data moves seamlessly between their apps.
If you're building agents, you can use individual Integry App Actions called Functions. We provide several popular agent framework support.
We provide managed authentication for Flows and Functions, including setup UI, credentials lifecycle management and more.
Here are the key concepts that you need to know to use Integry.
A flow moves data from one app to another. It is comprised of one or more blocks that run and execute steps when triggered. Flows sync data to your app, from your app, or both. Learn how to You can also do our as well.
A (trigger) block is comprised of one trigger and one or more subsequent steps. Each block must have a trigger that will run the block.
A trigger is an event, a poll, a webhook, or a scheduler that runs a block of an integration of a flow.
A query pulls data from an API endpoint by making one (or more) HTTP call(s). It can be used as a step, or as the source of a dynamic dropdown, custom fields, etc.
An action pushes data to an API endpoint by making an HTTP call.
The setup form of a flow is what a user sees when they are setting up an integration of the flow. It can have one or more pages, and a page can have one or more fields.
A tag is a piece of text you can use to label flows to selectively show them in the widget.
All HTTP calls made by Integry to any API endpoint are authenticated. If it's a call to your app, it will use an API key. If it's a call to another app, it will use OAuth 2.0 (if supported -- you can use your own developer app), or another such method.
Before they setup an integration of a flow with an app, users will have to connect to that app to give Integry access to their account in that app. You can allow users to connect and setup integrations with multiple accounts of an app.
A block of an integration runs when it is triggered by an event, on a schedule, or by a user action, and executes one or more steps in the block.
A task is a step that executes an HTTP call or runs custom code. If such a step is in a loop, a task will be charged every time that step executes in a run.
A workspace is your organization's private space for building and launching flows and managing integrations created by your users. Organizations with an Enterprise account can create multiple workspaces.
A run executes one or more steps in the flow. A step can be a query, an action, a control step, a condition, or execute custom code. Some steps are considered and are charged.
The marketplace is what you embed in your app using the SDK so your users can setup integrations. You can control what flows to show by tagging them, and filtering on those tags. The widget emits a number of different that you can leverage to control the user journey.
A user is a user of your app who will setup integrations with other apps using the Integry widget embedded within your app.
An app (or "application") is a web application that you can make HTTP calls to, or receive HTTP calls from, in a flow. It could be your application (referred to as "your app") or a third-party application like Mailchimp (referred to as "another app" or "third-party apps"). All calls from Integry to any app are .
An integration is an instance of a flow with a third-party app setup by your user using a of that app. You can allow users to setup one or more integrations of a flow.
