# Welcome

Integry helps software builders add user-facing integrations inside their apps and AI. Integry is a full-stack integration platform and we provide everything you need to build, delivery, scale, manage and support integrations. 

### Jump right in

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Functions</strong></td><td>Start here if you're adding integrations to your AI, Agent or Copilot.</td><td></td><td></td><td><a href="/pages/CyH2xJQs9yWJ1S8BYNav">/pages/CyH2xJQs9yWJ1S8BYNav</a></td></tr><tr><td><strong>Flows</strong></td><td>Start here if you want to build workflow-style integrations for your users.</td><td></td><td></td><td><a href="/pages/JjjojIyKxaiBPzzLwvtg">/pages/JjjojIyKxaiBPzzLwvtg</a></td></tr><tr><td><strong>APIs and SDKs</strong></td><td>Get up and running with SDKs and APIs.</td><td></td><td></td><td><a href="/pages/gmSdfowveMA2sD7cOquJ">/pages/gmSdfowveMA2sD7cOquJ</a></td></tr></tbody></table>


# Getting Started

## What is Integry? <a href="#h_01hqnsten2zpbbqw08fwb0psje" id="h_01hqnsten2zpbbqw08fwb0psje"></a>

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.&#x20;

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.

## Flow <a href="#h_01hnbfr5vv3pygsg5gddx48qdc" id="h_01hnbfr5vv3pygsg5gddx48qdc"></a>

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 [from another app](/flows/markdown/sync-data-from-another-app-to-your-app) to your app, [to another app](/flows/markdown/sync-data-to-another-app-from-your-app) from your app, or both. Learn how to [build a flow.](/flows/editor) You can also do our [AI Quickstart](https://docs.integry.ai/hc/en-us/articles/28305439384473-AI-Quickstart) as well.

<figure><img src="https://docs.integry.ai/hc/article_attachments/28183793226649" alt=""><figcaption></figcaption></figure>

## Block <a href="#h_01hnbfr93q0v3w0d65rg0mgacj" id="h_01hnbfr93q0v3w0d65rg0mgacj"></a>

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.

<figure><img src="/files/XYdxZM2Q3EldYgaWzTbV" alt=""><figcaption></figcaption></figure>

## Trigger <a href="#h_01hnbh26nyfh3rkp2jd3gwwcnp" id="h_01hnbh26nyfh3rkp2jd3gwwcnp"></a>

A **trigger** is an event, a poll, a webhook, or a scheduler that runs a block of an integration of a flow.

## Step <a href="#h_01hnbh34tmjhr6bt4zt1datn1c" id="h_01hnbh34tmjhr6bt4zt1datn1c"></a>

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 [tasks](#h_01hnbhz2dst2q97m0pn2en40xj) and are charged.

## Query <a href="#h_01hnbhrzmymy75tjrbm82s9yzg" id="h_01hnbhrzmymy75tjrbm82s9yzg"></a>

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.

## Action <a href="#h_01hnbhs1k1cn1knfzgcx5tqvdj" id="h_01hnbhs1k1cn1knfzgcx5tqvdj"></a>

An action pushes data to an API endpoint by making an HTTP call.

## Setup form <a href="#h_01hnbh34tk0tzxzq6zrwrktvm4" id="h_01hnbh34tk0tzxzq6zrwrktvm4"></a>

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.

<figure><img src="/files/pDtNWMG05ZM75Lcmy5kI" alt=""><figcaption></figcaption></figure>

## Marketplace <a href="#h_01hnbh34tm0bzhbpt0k9p0gnqd" id="h_01hnbh34tm0bzhbpt0k9p0gnqd"></a>

The marketplace is what you [embed in your app](broken://pages/3ocPBOvWARUN7bAf1292) 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 [events](/apis-and-sdks/js-sdk-reference/events) that you can leverage to control the user journey.

<figure><img src="/files/RukEzLPKFJQkcdeXw9Zx" alt=""><figcaption></figcaption></figure>

## Tag <a href="#h_01hnbk5zapq1tyf4ntsgmz8pss" id="h_01hnbk5zapq1tyf4ntsgmz8pss"></a>

A tag is a piece of text you can use to label flows to selectively show them in the [widget](broken://pages/BK1xCAWa6HEyHcDU8Oxr).

## User <a href="#h_01hnbk5zapk504515xhby98h3s" id="h_01hnbk5zapk504515xhby98h3s"></a>

A user is a user of your app who will setup integrations with other apps using the Integry widget embedded  within your app. [Learn more...](/users-and-billing/how-does-pricing-work)

## App <a href="#h_01hnbqkn50yx6g99ss7kk8v4ek" id="h_01hnbqkn50yx6g99ss7kk8v4ek"></a>

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 [authenticated](#h_01hnbqkn504cjnvrj2qb0drkwb).

## Authentication <a href="#h_01hnbqkn504cjnvrj2qb0drkwb" id="h_01hnbqkn504cjnvrj2qb0drkwb"></a>

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.

## Account <a href="#h_01hnbkcnwepqwy0cpan8nxb3gq" id="h_01hnbkcnwepqwy0cpan8nxb3gq"></a>

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.&#x20;

## Integration <a href="#h_01hnbfrb883b2v83p77esmk0xn" id="h_01hnbfrb883b2v83p77esmk0xn"></a>

An **integration** is an instance of a flow with a third-party app setup by your user using a [account](#h_01hnbkcnwepqwy0cpan8nxb3gq) of that app. You can allow users to setup one or more integrations of a flow.&#x20;

<figure><img src="/files/1j22JmSJ1iiEvj5dWxU1" alt=""><figcaption></figcaption></figure>

## Run <a href="#h_01hnbfrd7hb30hzw0nc853fcxd" id="h_01hnbfrd7hb30hzw0nc853fcxd"></a>

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.

## Task <a href="#h_01hnbhz2dst2q97m0pn2en40xj" id="h_01hnbhz2dst2q97m0pn2en40xj"></a>

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.

## Workspace <a href="#h_01hnjq030nre13cev40r2mxt2y" id="h_01hnjq030nre13cev40r2mxt2y"></a>

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.&#x20;


# Overview

Integry support hundreds of apps. See the full list [here](https://www.integry.ai/apps).

### What can I do with a supported app?

#### Connect to the App

Your users can connect to the app. Integry manages the authentication process and refreshes tokens (if applicable). For more, see [Authentication](/apps/authentication).

#### Call Functions

You can call functions to push/pull data to/from that app. Make a [`GET /functions?app=<app_name>`](https://integry.gitbook.io/docs/apis-and-sdks/api-reference#list-all-functions) call to find out what's possible. For more, see [Functions](/functions/overview).

#### Build Flows

You can build complex workflows that sync data one-way between your app and another app, or sync data bi-directionally. For more, see [Flows](/flows/overview).

#### Make Passthrough Requests

If you'd rather just consume the app's endpoints directly (while Integry manages auth), you can do that too! Simply make [Passthrough Requests](/apps/passthrough-requests).

### What if Integry does not have the app I need?

If we're able to access it, we'll be happy to add it! Our apps roadmap is entirely customer-driven. Tell us what you're looking for?


# Authentication

When your user click an app's name in the Integry marketplace, or you directly call [`connectApp()`](/apis-and-sdks/js-sdk-reference#connect-an-app) or [`showApp()`](/apis-and-sdks/js-sdk-reference#show-an-app-beta), Integry asks the user to connect their account in that app. Once they connect, Integry automatically adds the user's auth credentials in onwards HTTP requests to that app.

The authentication process for some apps may be as Basic as asking for a username and password that Integry will include in the Headers of HTTP requests. Many apps today require using the [OAuth 2.0](https://oauth.net/2/) protocol to get an access token that Integry will include in the HTTP request. If the token has expired, Integry will refresh the token and retry the request.

## Authentication types

### OAuth 2.0

#### Use Integry's developer app for OAuth 2.0

By default, most apps that use OAuth 2.0 for authentication are configured to use Integry's built-in developer app. This means that we don't make you set up a new developer app to perform actions in that app. That said, whenever you're ready to do it, you can simply switch to [using your developer app for OAuth 2.0.](#use-your-developer-app-for-oauth-2.0)

*Note: Some apps like Zoom can only be connected with your developer app. Follow the same steps below to provide your developer app credentials and you're all set.*

#### Use your developer app for OAuth 2.0

In this tutorial, we white-label OAuth 2.0 for HubSpot by creating a developer app in your HubSpot developer account. Skip to step 10 if you already have a developer app. We don't have guides for other apps but the steps will be quite similar.

1. Go to HubSpot's [developer site](https://app.hubspot.com/developer/).
2. Enter your login credentials.
   * If you don't have a developer account on HubSpot, you can create [one for free](https://developers.hubspot.com/get-started).
3. Go to Apps.

   <figure><img src="/files/KvzjYMFRDCBowwoqvQTJ" alt=""><figcaption></figcaption></figure>
4. Click "Create app".

   <figure><img src="/files/cx6SJNvilMhzFRAYhyft" alt=""><figcaption></figcaption></figure>
5. In the "App Info" tab, enter your app's name.

   * The name you enter here will appear on the authentication and authorization screens when your users will set up a flow with HubSpot.

   <figure><img src="/files/EMHlsnIFhqY7cUf2UOgx" alt=""><figcaption></figcaption></figure>
6. Upload your app's logo.

   * The logo you upload here will appear on the authentication and authorization screens when your users will set up a flow with HubSpot.

   <figure><img src="/files/r6htWbWgw70VM8Py20ko" alt=""><figcaption></figcaption></figure>
7. Go to the Auth tab and enter [`https://app.integry.io/auth/redirect/`](https://app.integry.io/auth/redirect/) as the redirect URL.

   * When your users connect their HubSpot account while setting up the integration, they will be taken to HubSpot's authentication server. After being verified by the authentication server, they will be redirected to the above URL.&#x20;

   <figure><img src="/files/DLaN2ectFLskPFtHVxQ2" alt=""><figcaption></figcaption></figure>
8. Scroll down to select scopes.
   * Scopes will determine the permissions to read/write data from/in your HubSpot account.
   * Select the following scopes:
     * `crm.schemas.deals.readcrm.objects.contacts.readcrm.objects.contacts.writecrm.objects.companies.readcrm.objects.companies.writecrm.lists.readcrm.lists.writecrm.objects.deals.readcrm.objects.deals.writecrm.schemas.contacts.readcrm.schemas.companies.readcontentoauth`
   * Copy each scope and paste it in the search bar.

     <figure><img src="/files/offUemDKcOKuc72I9j4g" alt=""><figcaption></figcaption></figure>
   * Select the "read" or "write" permission by clicking the checkbox. Your selected scope will be added.

     <figure><img src="/files/Wdz7H9NODOzyyJvxxoHO" alt=""><figcaption></figcaption></figure>
   * This is how the permissions section will appear on the authorization screen for your users.

     <figure><img src="/files/M89EojIBt8sSINWvsM2F" alt=""><figcaption></figcaption></figure>
9. Click on Create App. When your app is created, a "Client ID" and "Client secret" will be generated for your developer app. Go to the "Auth" tab to copy your Client ID and Client secret. You will use these credentials while configuring white-labeled OAuth in Integry.

   <figure><img src="/files/UD471ZkAW7lZGlLHOK9F" alt=""><figcaption></figcaption></figure>
10. Go to the 'Flows' tab.
11. Click on the three-dots menu for flow with HubSpot.
12. Click on 'Auth Settings.
13. Enter your Client ID, Client secret, and scopes in the respective fields.
    * The scopes you enter here should match with the scopes you select in your developer app.
    * Copy scopes from here: `content oauth crm.schemas.deals.read crm.objects.contacts.write crm.objects.companies.write crm.lists.write crm.objects.companies.read crm.lists.read crm.objects.deals.read crm.schemas.contacts.read crm.objects.deals.write crm.objects.contacts.read crm.schemas.companies.read`

      <figure><img src="/files/0HL7hylGhsb1qZZCfeuT" alt=""><figcaption></figcaption></figure>
14. Click Tes&#x74;**.**
    * As a result, an authentication UI opens up in your browser.
    * After a successful login, an authorization UI opens in your browser. The permissions you see here are the scopes you selected while creating your app. Click on Connect app.

      <figure><img src="/files/jYOhIWnLbtOpLCVi5wrM" alt=""><figcaption></figcaption></figure>
15. If your test is successful, you'll see a green tick.

    <figure><img src="/files/uk1HVVvpUD6keVdxb6kz" alt=""><figcaption></figcaption></figure>
16. In case of an error, you'll see an error icon, click 'See details' to view error details.

    * You'll see the steps performed by Integry on behalf of Doneday to authenticate and authorize the user. Check the Network Code to see which step failed.

      <figure><img src="/files/2PrrrSsfqikIozQIcCdq" alt=""><figcaption></figcaption></figure>
    * Click "View Payload" to see the details of the API call and troubleshoot accordingly. Here are some potential error messages you may encounter:
      * `invalid_grant`: Indicates that the OAuth client key or secret is not properly configured with the necessary grants or scopes
      * `BAD_CLIENT_SECRET`: Indicates an invalid or incorrect client secret was provided
      * `Unauthorized`: Indicates that the client key or secret provided is not authorized to perform the requested action

    <figure><img src="/files/aDeQuxPqqUwYN01kDZlO" alt=""><figcaption></figcaption></figure>
17. Click on Enable to enable white-labeled OAuth in your flows.

    <figure><img src="/files/00g2moV9YV5Cqf3YvLIJ" alt=""><figcaption></figcaption></figure>

Once enabled, any new users who set up integrations with Hubspot will see your app's branding (instead of Integry) on the Hubspot authorization screen, and we will use your developer app when we call Hubspot's API on their behalf. However, existing integrations will continue to use Integry's developer app because that's what the existing users used to login. If/When they disconnect their Hubspot account and reconnect, they will also login using your developer app (and not see Integry).

### API-Key <a href="#h_01hyd00d82nvkf3cpgaejgm51m" id="h_01hyd00d82nvkf3cpgaejgm51m"></a>

API-key based authorization type is known for its simplicity. The end-user signs into TPA, gets their API key, and copies it in their application to use. API-key is the name given to a secret token that is submitted to a web service along with a request. The key identifies the end-user in the TPA and performs an API request on behalf of that end-user. For the scope of Integry, once you enter your API-key while authenticating, Integry will consume your API-key for future communication.&#x20;

API-key based authentication is not a highly recommended auth type due to security loopholes. As an entity gets hold of the end-user's API key, they have to keep it safe (just like a password), because it maybe dangerous if an unauthorized entity accesses it.&#x20;

### API-Key and Secret <a href="#h_01hyd00d824zawdddcmr4dza8f" id="h_01hyd00d824zawdddcmr4dza8f"></a>

This is a modification of API-key. A combination of API-key and API Secret is used for authentication. It works the same as API-key. When an application is registered with the API, it generates a key and a secret for that application. Whenever the application makes a request, its request consists of the key and secret as well.&#x20;

### API-Key with URL <a href="#h_01hyd00d824y35s559v9fm5zcx" id="h_01hyd00d824y35s559v9fm5zcx"></a>

This works the same as API key, but the API calls are sent to the URL specified by the end-user while they're authenticating their TPA accounts.&#x20;

### Basic <a href="#h_01hyd00d8215cdess603v0q1qe" id="h_01hyd00d8215cdess603v0q1qe"></a>

It only requires a username and password for authentication. It is the least recommended way of authentication.

### Basic with URL <a href="#h_01hyd00d82xfgw4kjg26tgmab9" id="h_01hyd00d82xfgw4kjg26tgmab9"></a>

In addition to their username and password, it requires your end-users to provide a custom URL.

### Basic with API-Key <a href="#h_01hyd00d82jnkyy85qv0xxkr67" id="h_01hyd00d82jnkyy85qv0xxkr67"></a>

In addition to their username and password, it requires your end-users to provide a custom authorization URL and an API-key.

## Connect one/multiple account(s)

By default, all apps are configured to allow a user to connect one account per app. To allow multiple connected accounts for an app, do the following:

1. Go to Public Apps.
2. Click the configure button for the app.
3. Go to Authentication.
4. Set "Users can connect" to "Multiple accounts".

Note: Once a user has connected multiple accounts for an app, you must include a `connectedAccountID` when you call [`disconnectApp()`](/apis-and-sdks/js-sdk-reference#disconnect-an-app), [`showFunctionUI()`](/apis-and-sdks/js-sdk-reference#show-the-function-ui) and [`invokeFunction()`](/apis-and-sdks/js-sdk-reference#call-a-function). You can call [`getConnectedAccounts()`](/apis-and-sdks/js-sdk-reference#get-connected-accounts-of-an-app) to get the list of connected accounts for an app.


# Access Control and Testing

## Controlling access

You control the access of each app in your workspace. They can be accessed by:

* All users
* [Beta users only](/users/testing-with-beta-users)
* No one

### Configure access for an App

1. Go to Apps.
2. Click an app to open configure screen.
3. Toggle to Access.
4. Set **The app can be accessed by** to the desired option.

## Testing

Beta users can test apps, functions or flows from within the Integry app, or from the embedded UI in your app.

### Testing from the Integry app

Go to Apps and click **View as a User**.

It opens the embeddable UI in a modal. This view is **live**, i.e., you are accessing it as a real user, and all changes you make will impact connected accounts of the selected user.

{% hint style="info" %}
By default, your user ID will be selected. If you want, you can select a different user to **impersonate** but please remember that this is **live** and changes cannot be reversed.
{% endhint %}

If the selected user is a Beta User, you should see additional apps that only Beta users can access. Feel free to test your new ideas. When you're ready to release them, go back and make the app accessible to *All users*.

### Testing in your app

The embedded UI in your app will automatically show additional apps that only Beta users can access. No further action is needed in Integry.

Feel free to test your new ideas. When you're ready to release them, go back to the Integry app and make the app accessible to *All users*.


# Passthrough Requests

We have Functions for the most commonly used endpoints of 200+ apps.

If you want to do anything else, you can call the **Passthrough Request** function of any app we support via [API endpoint](#make-a-passthrough-request-via-api) or [SDK method](#make-a-passthrough-request-via-sdk). Integry will automatically add the user's auth credentials to the request.

### Make a passthrough request via API

<mark style="color:green;">`POST`</mark> `/<app_name>-passthrough-request`

Integry will execute the function if the user has already connected their account for the function app, and the `method` and `URL` parameters are provided in the body. These function calls will show in the Function Calls log in [the Integry app](https://app.integry.io/platform/functions/calls-log).

Integry will not execute the function if the user has not connected an account, or the parameters passed are invalid. These function calls will not show in the Function Calls log.

#### **Body**

| Name   | Type   | Description    | Required |
| ------ | ------ | -------------- | -------- |
| method | string | Request method | true     |
| url    | string | Request URL    | true     |
| body   | object | Request body   | false    |

#### **Response**

If Integry executes the function, it will respond with a `200 OK` with following keys in the response body:

* `network_code`: HTTP response status code of the onwards API call made by Integry.
* `output`: HTTP response body of the onwards API call made by Integry.

If Integry does not execute the function, it will respond with a `400 Bad Request` with following keys in the response body:

* `error`: Summary of the error.
* `error_details[]`: Detailed errors for individual fields (if applicable).

{% tabs %}
{% tab title="200" %}
{% code lineNumbers="true" %}

```json
// Function name: slack-passthrough-request
// GET https://slack.com/api/conversations.list?limit=2

{
    "network_code": "200",
    "output": {
        "ok": true,
        "channels": [
            {
                "id": "C6F3LQ03A",
                "name": "random",
                "is_channel": true,
                "is_group": false,
                "is_im": false,
                "is_mpim": false,
                "is_private": false,
                "created": 1501486653,
                "is_archived": false,
                "is_general": false,
                "unlinked": 0,
                "name_normalized": "random",
                "is_shared": false,
                "is_org_shared": false,
                "is_pending_ext_shared": false,
                "pending_shared": [],
                "context_team_id": "T6F74R6TB",
                "updated": 1724807678577,
                "parent_conversation": null,
                "creator": "U6GKMKPE2",
                "is_ext_shared": false,
                "shared_team_ids": [
                    "T6F74R6TB"
                ],
                "pending_connected_team_ids": [],
                "is_member": true,
                "topic": {
                    "value": "Non-work banter and water cooler conversation",
                    "creator": "U6GKMKPE2",
                    "last_set": 1501486653
                },
                "purpose": {
                    "value": "A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.",
                    "creator": "U6GKMKPE2",
                    "last_set": 1501486653
                },
                "properties": {
                    "tabs": [
                        {
                            "id": "files",
                            "label": "",
                            "type": "files"
                        }
                    ]
                },
                "previous_names": [],
                "num_members": 7
            },
            {
                "id": "C6GKMKRUN",
                "name": "general",
                "is_channel": true,
                "is_group": false,
                "is_im": false,
                "is_mpim": false,
                "is_private": false,
                "created": 1501486653,
                "is_archived": false,
                "is_general": true,
                "unlinked": 0,
                "name_normalized": "general",
                "is_shared": false,
                "is_org_shared": false,
                "is_pending_ext_shared": false,
                "pending_shared": [],
                "context_team_id": "T6F74R6TB",
                "updated": 1731095674264,
                "parent_conversation": null,
                "creator": "U6GKMKPE2",
                "is_ext_shared": false,
                "shared_team_ids": [
                    "T6F74R6TB"
                ],
                "pending_connected_team_ids": [],
                "is_member": true,
                "topic": {
                    "value": "Channel for high priority, company-wide announcements and work-related matters. If you want to banter please head over to <#C02D3JZA45T|> if you want to discuss low priority items head over to <#G01L3PW2A01|integry-internal>",
                    "creator": "U6FQESQ02",
                    "last_set": 1632860908
                },
                "purpose": {
                    "value": "This channel is for team-wide communication and announcements. All team members are in this channel.",
                    "creator": "U6GKMKPE2",
                    "last_set": 1501486653
                },
                "properties": {
                    "tabs": [
                        {
                            "id": "files",
                            "label": "",
                            "type": "files"
                        }
                    ]
                },
                "previous_names": [],
                "num_members": 14
            }
        ],
        "response_metadata": {
            "next_cursor": "dGVhbTpDOFBLNUhOOTU="
        }
    }
}
```

{% endcode %}
{% endtab %}

{% tab title="400" %}

```json
// Function name: slack-passthrough-request
// Outcome: Error -- app was not connected
{
    "error": "Could not call the function due to invalid input. Please see `error_details` for further information.",
    "error_details": [
        "User has not connected their Slack account. To connect an account, please call following SDK method: `connectApp('slack')`"
    ]
}
```

{% endtab %}
{% endtabs %}

### Make a passthrough request via SDK

`invokeFunction(<app_name>-passthrough-request, params, connectedAccountId)`

Integry will execute the function if the user has already connected their account for the function app, and the `method` and `URL` parameters are provided in the `params` object. These function calls will show in the Function Calls log in [the Integry app](https://app.integry.io/platform/functions/calls-log).

Integry will not execute the function if the user has not connected an account, or the parameters passed are invalid. These function calls will not show in the Function Calls log.

```javascript
const params = {
  method: "GET",
  url: "https://slack.com/api/conversations.list?limit=2"
};
integry.invokeFunction("slack-passthrough-request", params).then((result) => {
  console.log("Received response from Slack:", result);
}).catch((error) => {
  console.error("Failed to invoke function:", error);
});
```

#### Method parameters

<table><thead><tr><th width="140">Name</th><th width="83">Type</th><th width="319">Description</th><th width="129">Example</th><th>Required</th></tr></thead><tbody><tr><td><code>functionName</code></td><td>string</td><td>The name of the function to execute</td><td>slack-post-message</td><td>true</td></tr><tr><td><code>params</code></td><td>object</td><td>An object containing the function parameters.</td><td><p>{"method":"",</p><p>"url":"",</p><p>"body":""}</p></td><td>true</td></tr><tr><td><code>connectedAccountId</code></td><td>string</td><td>The connected account to use for executing the action. Only use if the user has connected multiple accounts.</td><td>43654</td><td>false</td></tr></tbody></table>

#### **Returns**

If Integry executes the function, this method returns a `result` object with following keys:

* `network_code`: HTTP response status code of the onwards API call made by Integry.
* `output`: HTTP response body of the onwards API call made by Integry.

If Integry does not execute the function, this method returns a `result` object with following keys:

* `error`: Summary of the error.
* `error_details[]`: Detailed errors for individual fields (if applicable).

{% tabs %}
{% tab title="Result" %}
{% code lineNumbers="true" %}

```json
// Function name: pipedrive-passthrough-request
// POST https://api.pipedrive.com/api/v2/persons
{
    "network_code": "200",
    "output": {
        "success": true,
        "data": {
            "id": 27,
            "name": "Sample contact",
            "first_name": "Sample",
            "last_name": "contact",
            "add_time": "2024-11-11T17:18:18Z",
            "update_time": null,
            "visible_to": 3,
            "custom_fields": null,
            "owner_id": 22469411,
            "label_ids": [],
            "org_id": null,
            "is_deleted": false,
            "picture_id": null,
            "phones": [],
            "emails": []
        }
    }
}
```

{% endcode %}
{% endtab %}

{% tab title="Error" %}

```json
// Function name: pipedrive-passthrough-request
// POST https://api.pipedrive.com/api/v2/persons
{
    "error": "Could not call the function due to invalid input. Please see `error_details` for further information.",
    "error_details": [
        "User has not connected their Pipedrive account. To connect an account, please call following SDK method: `connect('pipedrive')`"
    ]
}
```

{% endtab %}
{% endtabs %}

### List all passthrough request functions

<mark style="color:green;">`GET`</mark> `/functions?type=passthrough`

List all passthrough request functions supported by Integry. See [`/functions`](https://integry.gitbook.io/integry-docs/apis-and-sdks/api-reference#list-all-functions) for more options.


# Supported Apps

Integry supports [hundreds of apps](https://www.integry.ai/apps). Specifics about some of them are linked on the left.


# Accelo

[Accelo](https://www.integry.io/apps/accelo) is an online platform to manage your projects, services, sales, and retainers. It is an intelligent system for project management, invoices and payments, and CRM features. It helps in tracking time and progress, managing CRM contacts, dealing with client requests, and also coordinating with your team. The Accelo App Connector syncs and manages contacts with other third-party apps.&#x20;

### Authentication  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Accelo uses [Basic](/apps/authentication#h_01hyd00d8215cdess603v0q1qe) authentication.

### Triggers <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Accelo uses poll-based triggers. Integry will send a request to Accelo every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Accelo acts as a trigger application) and perform an action in Accelo, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

In the Accelo App Connector, the custom fields are not supported in activities.


# Aircall

### Authentication <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Aircall uses Basic authentication with an App ID and API Token combination.&#x20;


# Constant Contact

Integry supports a number of triggers and actions of Constant Contact.

### Authentication <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Your users will login to Constant Contact via OAuth 2.0.

### Triggers <a href="#h_01hr556ap5m0d97s0v2hv9bk41" id="h_01hr556ap5m0d97s0v2hv9bk41"></a>

| **Name**                   | **Type** | **Description**                               |
| -------------------------- | -------- | --------------------------------------------- |
| **Email Campaign Created** | Polling  | Triggers when a new campaign is created       |
| Contact Created/Updated    | Polling  | Triggers when a contact is created or updated |

For more, please see [Constant Contact API docs](https://developer.constantcontact.com/api_reference/index.html).

### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**                     | **Method** | **Description**                           |
| ---------------------------- | ---------- | ----------------------------------------- |
| Create Email Campaign        | POST       | Creates a new email campaign              |
| Update Email Campaign's Name | PATCH      | Updates an existing email campaign's name |
| Delete Email Campaign        | DELETE     | Deletes an existing email campaign        |
| Delete Contact               | DELETE     | Deletes an existing contact               |
| Unsubscribe Contact          | PUT        | Unsubscribes an existing contact          |
| Create Contact               | POST       | Creates a new contact                     |
| Update Contact               | PATCH      | Updates an existing contact               |
| Get Contact by ID            | GET        | Fetches a contact details by ID           |
| Create Tag                   | POST       | Creates a new tag                         |

For more, please see [Constant Contact API docs](https://developer.constantcontact.com/api_reference/index.html).


# Copper

Integry supports a number of triggers and actions of Copper.

#### Authentication <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Copper uses OAuth 2.0.

#### Triggers <a href="#h_01hr556ap5m0d97s0v2hv9bk41" id="h_01hr556ap5m0d97s0v2hv9bk41"></a>

| **Name**               | **Type** | **Description**                              |
| ---------------------- | -------- | -------------------------------------------- |
| Company Created        | Polling  | Triggers when a new company is created       |
| Company Updated        | Polling  | Triggers when a new company is updated       |
| Company Deleted        | Instant  | Triggers when an existing company is deleted |
| Lead Created/Updated   | Polling  | Triggers when a lead is created or updated   |
| Opportunity Deleted    | Instant  | Triggers when a new opportunity is deleted   |
| Opportunity Created    | Polling  | Triggers when a new opportunity is created   |
| Opportunity Updated    | Polling  | Triggers when a new opportunity is updated   |
| Person Created         | Polling  | Triggers when a person is created            |
| Person Created/Updated | Polling  | Triggers when a person is created or updated |
| Task Created           | Polling  | Triggers when a new task is created          |
| Task Updated           | Polling  | Triggers when a task is updated              |
| Task Deleted           | Instant  | Triggers when an existing task is deleted    |

For more, please see [Copper API docs](https://developer.copper.com/).

#### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**            | **Method** | **Description**                                                           |
| ------------------- | ---------- | ------------------------------------------------------------------------- |
| Delete Company      | DELETE     | Deletes an existing company                                               |
| Create Company      | POST       | Creates a new company                                                     |
| Update Company      | PUT        | Updates an existing company                                               |
| Delete Lead         | DELETE     | Deletes an existing lead                                                  |
| Create Lead         | POST       | Creates a new lead                                                        |
| Update Lead         | PUT        | Updates an existing lead in your copper account                           |
| Get Lead by Email   | GET        | Fetches details of a lead record by email                                 |
| Get Lead by ID      | GET        | Fetches details of a lead by ID                                           |
| Upsert Lead         | PATCH      | Create a new lead if it does not match the criteria, else update the lead |
| Delete Task         | DELETE     | Deletes an existing task                                                  |
| Create Task         | POST       | Creates a new task                                                        |
| Update Task         | PUT        | Updates an existing task                                                  |
| Delete Opportunity  | DELETE     | Deletes an existing opportunity                                           |
| Create Opportunity  | POST       | Creates a new opportunity                                                 |
| Update Opportunity  | PUT        | Updates an existing opportunity                                           |
| Delete Person       | DELETE     | Deletes an existing person                                                |
| Create Person       | POST       | Creates a new person                                                      |
| Update Person       | PUT        | Updates an existing person                                                |
| Get Person by Email | GET        | Fetches details of a person record by email                               |
| Get Person by ID    | GET        | Fetches details of a person record by ID                                  |

For more, please see [Copper API docs](https://developer.copper.com/).


# Elastic Email

Integry supports a number of actions of Elastic email.

### Authentication <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Elastic Email uses API-Key authentication.

### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**        | **Method** | **Description**              |
| --------------- | ---------- | ---------------------------- |
| Create Contact  | POST       | Creates a new contact        |
| Update Contact  | PUT        | Updates an existing contact  |
| Create Template | POST       | Creates a new template       |
| Update Template | PUT        | Updates an existing template |
| Get Template    | GET        | Fetches an existing template |

For more, please see [Elastic Email API docs.](https://elasticemail.com/developers/api-documentation/rest-api)


# Fireflies

### Authentication <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Fireflies uses [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authentication.


# Insightly

[Insightly](https://www.integry.io/apps/insightly) is a customer relationship manager that combines marketing, sales, service, and projects. Its marketing automation helps you build new customer relationships and strengthen existing ones. In addition, you can track real-time campaign performance and ROI. The Insightly App Connector enables to sync and manage contacts with other third-party apps.&#x20;

Integry supports a number actions in Insightly.

#### Authentication <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Insightly uses API Key+URL authentication.

### Triggers <a href="#h_01hr556ap5m0d97s0v2hv9bk41" id="h_01hr556ap5m0d97s0v2hv9bk41"></a>

The triggers used in Insightly are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Insightly every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Insightly acts as a trigger application) and perform an action in Insightly, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

| **Name**                | **Type** | **Description**                                                      |
| ----------------------- | -------- | -------------------------------------------------------------------- |
| Event Created           | Polling  | Triggers when an event is created                                    |
| Contact Created         | Polling  | Triggers when a contact is created                                   |
| Lead Created            | Polling  | Triggers when a lead is created                                      |
| Event Created/Updated   | Polling  | Triggers when an existing event is updated or a new one is created   |
| Contact Created/Updated | Polling  | Triggers when an existing contact is updated or a new one is created |
| Lead Created/Updated    | Polling  | Triggers when an existing lead is updated or a new one is created    |

For more, please see [Insightly API docs](https://api.na1.insightly.com/v3.1/).

#### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**              | **Method** | **Description**                                                                                        |
| --------------------- | ---------- | ------------------------------------------------------------------------------------------------------ |
| Delete Contact        | DELETE     | Deletes an existing contact                                                                            |
| Create Contact        | POST       | Creates a new contact                                                                                  |
| Get Contact by ID     | GET        | Fetch the details of a contact using ID                                                                |
| Update Contact        | PUT        | Updates an existing contact                                                                            |
| Get Contacts by Email | GET        | Retrieve the list of contacts that match the email address. Only the top 50 contacts will be returned. |
| Get Event by ID       | GET        | Fetch the details of an event using ID                                                                 |
| Create Event          | POST       | Creates a new event on your calendar.                                                                  |
| Get Lead by ID        | GET        | Fetch the details of a lead using ID                                                                   |
| Create Lead           | POST       | Creates a new lead                                                                                     |
| Update Lead           | PUT        | Updates an existing lead                                                                               |
| Get Leads by Email    | GET        | Retrieve the list of leads that match the email address. Only the top 50 leads will be returned.       |
| Get Object by ID      | GET        | Fetches the details of object by their ID                                                              |


# Instantly

Integry supports a number of actions of Instantly.

### Authentication <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Instantly uses [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authenticaiton.

### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**    | **Method** | **Description**          |
| ----------- | ---------- | ------------------------ |
| Add Lead    | POST       | Adds leads to a campaign |
| Update Lead | POST       | Updates an existing lead |

For more, please see [Instantly API docs](https://developer.instantly.ai/introduction).


# Ontraport

Integry supports a number of triggers and actions of Ontraport.

### Authentication <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Ontraport uses API key + secret authentication.

### Triggers <a href="#h_01hr556ap5m0d97s0v2hv9bk41" id="h_01hr556ap5m0d97s0v2hv9bk41"></a>

| **Name**         | **Type** | **Description**                              |
| ---------------- | -------- | -------------------------------------------- |
| Contact Created  | Webhook  | Triggers when a contact is created           |
| Product Created  | Polling  | Triggers when a product is created           |
| Deal Created     | Polling  | Triggers when a deal is created              |
| Company Created  | Polling  | Triggers when a company is created           |
| Campaign Created | Webhook  | Triggers when a campaign is created          |
| Product Deleted  | Polling  | Triggers when an existing product is deleted |
| Company Updated  | Polling  | Triggers when a company is updated           |
| Deal Updated     | Polling  | Triggers when a deal is updated              |
| Create Product   | Webhook  | Creates a new product                        |
| Update Product   | Webhook  | Updates an existing product                  |
| Delete Product   | Webhook  | Deletes an existing product                  |

For more, please see [Ontraport API docs](https://api.ontraport.com/doc/).

## Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**        | **Method** | **Description**                       |
| --------------- | ---------- | ------------------------------------- |
| Create Contact  | POST       | Creates a new contact in your account |
| Create Campaign | POST       | Creates a new campaign                |
| Create Company  | POST       | Creates a new company                 |
| Update Company  | PUT        | Updates an existing company           |
| Delete Contact  | DELETE     | Deletes an existing contact           |
| Update Contact  | PUT        | Updates an existing contact           |
| Create Deal     | POST       | Creates a new deal                    |
| Create Product  | POST       | Creates a new product                 |
| Update Product  | PUT        | Updates an existing product           |
| Delete Product  | DELETE     | Deletes an existing product           |


# RingCentral

Authorization

Your users will log in to RingCentral via OAuth 2.0 using Integry's developer app. You can [replace it](https://support.integry.io/hc/en-us/articles/10887314172441) by [setting up your own.](https://developers.ringcentral.com/guide/authentication/quick-start)\ <br>

#### FAQs <a href="#id-01hw60a621etfhwyaqdtv9jkj2" id="id-01hw60a621etfhwyaqdtv9jkj2"></a>

#### Which OAuth scopes are currently supported for RingCentral? <a href="#h_01j1w3rjnhw0xmt49rndnqqajy" id="h_01j1w3rjnhw0xmt49rndnqqajy"></a>

When authenticating to RingCentral via OAuth, we currently support a limited set of scopes. These scopes grant specific permissions to access various features within the RingCentral platform. Below is the list of scopes we support and the functionalities they allow:

* **ReadCallLog**: Access to view the user's call log data.
* **CallControl**: Manage and control ongoing calls.
* **Contacts**: Read access to the user's contacts.
* **SMS**: Send and receive SMS messages.
* **Analytics**: Access analytics and reports.
* **Faxes**: Send and manage faxes.
* **ReadAccounts**: Read account information.
* **ReadCallRecording**: View and manage call recordings.
* **Video**: Access video conferencing features.
* **RingOut**: Initiate calls from your RingCentral number using a different device.
* **TeamMessaging**: Use team messaging features within RingCentral.
* **InternalMessages**: Access and manage internal messages.
* **Faxes**: Send, receive, and manage faxes.

At the moment, only these scopes are available for integration. If additional scopes are required, please reach out to us with your request.


# Sendy

Integry supports the flowing actions of Sendy.

#### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**        | **Method** | **Description**        |
| --------------- | ---------- | ---------------------- |
| Create Campaign | POST       | Creates a new campaign |

For more, please see [Sendy API docs](https://sendy.co/api).

#### Authorization <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Sendy uses [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The end-user is identified by an API key, and Integry uses this key to perform an API request to Sendy on behalf of that end-user.

&#x20;

#### FAQs <a href="#id-01hw60a621etfhwyaqdtv9jkj2" id="id-01hw60a621etfhwyaqdtv9jkj2"></a>

**Why am I unable to send campaigns on Sendy?**\
If you're having trouble sending campaigns with Sendy, ensure that your account is fully configured. Initially, you need to set up your Sendy installation correctly by connecting it to an SMTP service, as Sendy does not have built-in capabilities to send emails on its own. Ensure that all SMTP settings are correctly entered in the 'Settings' section of your Sendy dashboard. This setup is essential for Sendy to function properly and send out campaigns.


# ServiceTitan

Authorization

Your users will authenticate to ServiceTitan via OAuth 2.0 using their own client credentials. You need to [set up your own OAuth app](https://developer.servicetitan.io/docs/get-going-manage-client-id-and-secret/) for this process.\ <br>

#### FAQs <a href="#id-01hw60a621etfhwyaqdtv9jkj2" id="id-01hw60a621etfhwyaqdtv9jkj2"></a>

#### Where can I find the Tenant ID in ServiceTitan? <a href="#h_01j1w3rjnhw0xmt49rndnqqajy" id="h_01j1w3rjnhw0xmt49rndnqqajy"></a>

To authenticate to ServiceTitan via OAuth, you will need your Tenant ID. Follow these steps to find your ServiceTitan Tenant ID:

1. **Sign in to ServiceTitan**: Log in to your ServiceTitan account with administrative privileges.
2. **Navigate to Settings**: Go to the settings menu from the main dashboard.
3. **Access API Integrations**: Within the settings, look for the section related to API integrations or OAuth settings.
4. **Find Tenant ID**: The Tenant ID will be listed under the API integration settings. It might be labeled as "Tenant ID" or "Account ID".


# ActiveCampaign

[ActiveCampaign](https://www.integry.io/apps/activecampaign) is an automated email marketing app. You can use it to send personalized content to your end-users based on their interests and past actions. It also helps to create automated workflows. The ActiveCampaign App Connector manages and syncs contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Insightly account with ActiveCampaign, you can go through some basic specifications of the ActiveCampaign App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

ActiveCampaign uses an [API Key + URL](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) based authentication. Both the API key and the URL to your instance can be found inside the settings of your Active Campaign account.

#### &#x20;

#### Trigger Type <a href="#trigger-type-0-3" id="trigger-type-0-3"></a>

ActiveCampaign connector supports both [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/) and [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers.

* Contact object has poll-based triggers. This means for the contact object, Integry will send a request to ActiveCampaign every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which ActiveCampaign acts as a trigger application) and perform an action in ActiveCampaign, expect a 5-minute delay for the trigger to be received at Integry.
* Campaign and Deal objects have webhook-based triggers. Therefore, for campaign and deal objects, Integry will receive the trigger instantly, as soon as an event occurs.

#### Limitations <a href="#limitations-0-4" id="limitations-0-4"></a>

The following types of custom fields are not supported for mapping in the triggers/queries:

* List box
* Dropdown
* Checkbox
* Radio


# Jotform

Integry supports a number of triggers and actions of Jotform.

#### Triggers <a href="#h_01hr556ap5m0d97s0v2hv9bk41" id="h_01hr556ap5m0d97s0v2hv9bk41"></a>

| **Name**                | **Type** | **Description**                            |
| ----------------------- | -------- | ------------------------------------------ |
| Form Submitted          | Polling  | Triggers when a form is submitted          |
| Form Submission Updated | Polling  | Triggers when a form submission is updated |

For more, please see [Jotform API docs](https://api.jotform.com/docs/). If you're not sure how triggers work in Integry, go [here](https://support.integry.io/hc/en-us/articles/29484874325017).

#### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**               | **Method** | **Description**               |
| ---------------------- | ---------- | ----------------------------- |
| Create Form Submission | POST       | Creates a new form Submission |

For more, please see [Jotform API docs](https://api.jotform.com/docs/).

#### Authorization <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Jotform uses [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The end-user is identified by an API key, and Integry uses this key to perform an API request to ActiveTrail on behalf of that end-user.


# ActiveTrail

[ActiveTrail](https://www.integry.io/apps/activetrail) is a well-known web-based app for email marketing. The ActiveTrail App Connector manages and syncs templates with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the ActiveTrail App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

ActiveTrail uses [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The end-user is identified by an API key, and Integry uses this key to perform an API request to ActiveTrail on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

No trigger is present in the ActiveTrail app as of now.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

The thumbnails for templates created via API do not show up, however, the content appears fine.


# Agile CRM

[Agile CRM](https://www.integry.io/apps/agile-crm) is a customer relationship management software. It offers sales, marketing, and service CRM for small businesses. You can manage your contacts, and appointments along with one-click calling, and voicemail automation. In addition to managing your projects, you can also create marketing campaigns and embed social media platforms in them using the Social Suite. The Agile CRM App Connector syncs and manages contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Insightly account with Agile CRM, you can go through some basic specifications of the Agile CRM App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Agile CRM uses a [Basic + URL](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The authorization does not expire in this case.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Agile CRM uses [webhook-based](https://support.integry.io/hc/en-us/articles/360021913434-Creating-Webhook-Triggers) triggers where upon setting up, Integry will generate a URL which the user has to paste inside the Agile CRM admin settings.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Following are the limitations of the Agile CRM App Connector as of now:

* Custom fields are not supported in the activities.
* Webhooks are only supported for Agile CRM Enterprise users.


# Aha!

The [Aha!](https://www.integry.io/apps/aha) app organizes and integrates content from the web between your phone and car for easy access on the go. It is an online tool to run your product campaigns, work on roadmaps, and chalk out detailed features and user stories. Aha! works with a bug tracking system for the timely execution of products and their features. The Aha! App Connector helps you sync and manage ideas with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Aha! account with Integry, here are a few things you need to learn about the Aha! App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Aha! uses [API key + URL](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. An API key and URL identify the end-user. Integry uses this key to perform an API request to Aha! on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in Aha! are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Aha! every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Aha! acts as a trigger application) and perform an action in Aha!, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Presently there are no limitations of the Aha! App Connector.


# Airtable

[Airtable](https://www.airtable.com/) is an online platform that allows you to create a custom database of apps tailored to your specific needs and workflows. It helps you to create a single source of features according to your team's work. It also helps you build custom interfaces that deliver relevant information to your team members, which they can use to plan their future actions. The Airtable App Connector syncs and manages records with other third-party apps.

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Airtable connector.

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Airtable uses the [API key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) based authorization method. The API key identifies the end-user, and Integry uses this key to perform an API communication with Airtable on behalf of that end-user.

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

No triggers are implemented in the Airtable App Connector.

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations of the Airtable App Connector.


# Amazon SES

[Amazon Simple Email Service (SES)](https://www.integry.io/apps/amazon-ses) is an email service that enables developers to send mail from within any application. It can easily be configured to support several email use cases, including transactional, marketing, or mass email communications. It offers flexible IP deployment and email authentication options to help drive higher deliverability and protect the sender's reputation. The Amazon SES App Connector helps you sync and manage email templates with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Amazon SES account with Integry, here are a few things you need to learn about the Amazon SES App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Amazon SES uses [API Key,](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) API Secret, and API Region type of authorization, where you have to provide both your API key and secret along with your AWS region.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Amazon SES supports [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers for email templates. Integry will send a request to Amazon SES every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Amazon SES acts as a trigger application) and perform an action in Amazon SES, expect a 5-minute delay for the trigger to be received at Integry.

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, the name of an email template cannot be updated.


# Asana

[Asana](https://asana.com/campaign/fac/think?\&utm_campaign=Brand--SA--EN--Core--All-Device--Exact\&utm_source=google\&utm_medium=pd_cpc_br\&gclid=CjwKCAiA76-dBhByEiwAA0_s9c3HeQuMbM4ngeIr6yYDLPkQ6r42jzaubA8sg-XyLW0mwsOnPz831xoCuCIQAvD_BwE\&gclsrc=aw.ds) is a project planning and tracking app. You can use it to keep an eye on your project's progress and discuss it among your team from one place. It helps you organize your tasks and connect with your teams over the internet remotely. It offers workflow templates that can be used to define your project's steps. The Asana App Connector syncs and manages projects, tasks, and tags with other third-party apps.

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Asana connector.

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Asana uses [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The access token expires in 1 hour and gets refreshed automatically after expiration.

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Currently, there are no triggers implemented.

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are the following limitations of the Asana App Connector:

* The format for the date field is YYYY-MM-DD.
* The start date of projects needs to be before the due date.


# Basecamp3

[Basecamp3](https://www.integry.io/apps/basecamp3) is an online tool to manage all your resources and data. It offers features like to-do lists, calendars, message boards, and much more. You can also collaborate with your team and participate in discussions to get a solid view of what's going on in your organization. The Basecamp3 App Connector helps you sync and manage messages, todos, and comments with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Basecamp3 account with Integry, here are a few things you need to learn about the Basecamp3 App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

It uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method. The access token expires in two weeks. A new access token is generated with the help of the refresh token.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Basecamp3 uses [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/) triggers. This means that as soon as an event occurs, Integry will receive the trigger instantly.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations for the Basecamp3 App Connector.


# BirdSend

[BirdSend](https://www.integry.io/apps/birdsend) is a cloud-based platform for email marketing that enables content creators to streamline marketing operations through drip email campaigns, contact segmentation, and revenue tracking. You can set up sequence or drip email campaigns on a single page to automatically follow up with your subscribers and make sales. You can also use it to send broadcast emails. BirdSend helps you sync and manage broadcasts and contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your BirdSend account with Integry, here are a few things you need to learn about the BirdSend App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

BirdSend uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The access token expires in 60 days and refresh token is implemented.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers used in BirdSend are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to BirdSend every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which BirdSend acts as a trigger application) and perform an action in BirdSend, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

While creating a contact, a sequence has to be LIVE for it to appear in the dropdown.


# Breezy HR

Breezy HR is an online recruiting tool where you can post new jobs, manage applicants, and recruit the most suitable resources. It helps in reporting and analytics as well. Breezy HR is an end-to-end applicant tracking platform that offers candidates pipelines, built-in scorecards, and interview guides. You can also use it to send bulk or individual custom emails, SMS, or even custom templates. The Breezy HR App Connector helps you sync and manage candidates with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Breezy HR account with Integry, here are a few things you need to learn about the Breezy HR App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Breezy HR uses the [Basic](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. A username and password identify the end-user. Integry uses this to perform an API request to Breezy HR on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in Breezy HR are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Breezy HR every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Breezy HR acts as a trigger application) and perform an action in Breezy HR, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there is no activity to delete candidates in the Breezy HR App Connector.


# Brevo

[Brevo](https://www.integry.io/apps/sendinblue) (formerly called Sendinblue) is a SaaS company that provides relationship marketing. Their app allows you to use their built-in templates to create customized newsletters. The app helps you automate your marketing using workflow templates and scheduled emails. You can also analyze your performance through built-in statistics and reports available in the app. The Sendinblue App Connector helps you sync and manage contacts with other third-party apps.&#x20;

### Specifications  <a href="#h_01hqrsyszwp9v28gdg4gke5kcg" id="h_01hqrsyszwp9v28gdg4gke5kcg"></a>

Before you connect your Sendinblue account with Integry, here are a few things you need to learn about the Sendinblue App Connector.&#x20;

#### Authorization Type  <a href="#h_01hqrsyszw1j97f4wsne703n8w" id="h_01hqrsyszw1j97f4wsne703n8w"></a>

Sendinblue uses [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The end-user is identified by an API key, and Integry uses this key to perform an API request to Sendinblue on behalf of that end-user.&#x20;

#### Trigger Type <a href="#h_01hqrsyszw51cxxz5ptwb34npj" id="h_01hqrsyszw51cxxz5ptwb34npj"></a>

Sendinblue uses [webhook-based ](https://tray.io/documentation/connectors/triggers/webhook-trigger/)triggers. Therefore, as soon as an event occurs, Integry will receive the trigger instantly.&#x20;

### Limitations <a href="#h_01hqrsyszwyt5nba3303wjtmeg" id="h_01hqrsyszwyt5nba3303wjtmeg"></a>

Currently, boolean and category type custom fields are not supported in mapping.


# Campaign Monitor

[Campaign Monitor](https://www.integry.io/apps/campaign-monitor) is an online email marketing and automation platform that helps users to create, send, manage, and track branded emails for themselves and their clients. It enables you to create personalized customer journeys and smart segments and send relevant emails to potential customers. It also offers campaign customization and template management. The Campaign Monitor App Connector helps sync with and manage your subscribers with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Campaign Monitor account with Integry, here are a few things you need to learn about the Campaign Monitor App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The Campaign Monitor App Connector uses the [OAuth2 ](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry)authorization type. The access token used here usually expires in 14 days, and once it expires, Integry makes an internal call to get a new access token.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Triggers in Campaign Monitor use [webhook](https://tray.io/documentation/connectors/triggers/webhook-trigger/) subscriptions. This means that as soon as an event occurs, Integry will receive the trigger instantly.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there is only one limitation of the Campaign Monitor App Connector. In triggers and queries, multi-select or single-select dropdowns are not supported for mapping.


# Capsule CRM

[Capsule CRM](https://www.integry.io/apps/capsule-crm) is an online customer relationship manager for individuals, small businesses, and sales teams wanting a simple, effective, and affordable solution. This tool keeps customer information along with easy history tracking. The Capsule CRM App Connector is multi-purpose and can be used to sync and manage people, opportunities, tasks, and cases between your Capsule CRM account and other third-party app accounts.&#x20;

### Specifications <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Capsule CRM account with Integry, here are a few things you need to learn about the Capsule CRM App Connector.&#x20;

#### Authorization Type <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Capsule CRM uses the [OAuth ](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry)authorization method where the access token expires after seven days. A refresh token is used to generate a new access token after it expires. This won't have any impact on current integrations if implemented properly. This authorization enables third-party applications (clients) to gain delegated access to protected resources in Capsule via an API. When setting up an integration, you need to allow Integry to use your Capsule CRM account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Triggers in Capsule CRM are [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). Therefore, Integry will listen for events happening inside your Capsule account.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

As of now, there are the following limitations in the Capsule CRM App Connector:

* Custom fields are not supported in queries.
* While creating/updating a person or an opportunity, you can only attach a single tag.
* You can only add a single email, social site, phone, and address while creating a person.


# Chargify

[Chargify](https://www.integry.io/apps/chargify) is a billing system for Web 2.0 and SaaS companies. It provides the revenue management tools you need for your business. Chargify enables you to manage billing and subscription for B2B SaaS customers. It also offers features like self-serve product plans, support for trial periods, complicated billing structures, and multiple payment collection options. The Chargify App Connector can help sync and manage customers with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Chargify account with Integry, here are a few things you need to learn about the Chargify App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Chargify uses a variant of [Basic+URL](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry). In order to authenticate, a user must enter their API key and password along with their instance URL.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Chargify supports [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to Chargify every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Chargify acts as a trigger application) and perform an action in Chargify, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, custom fields are not supported in query mapping in the Chargify App Connector.


# CleverReach

[CleverReach](https://www.integry.io/apps/cleverreach) is an email marketing platform. It helps you create automated email marketing campaigns for your customers. It also enables you to choose from the available templates to target your customers. You can manage your lists and user segments by designing personalized email campaigns for customers based on their geographic location, demographics, interests, etc. You can also gauge your email reach by analyzing client email reports and improving your campaigns. The CleverReach App Connector helps you manage and sync recipients with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the specifications of the CleverReach App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

CleverReach uses the [OAuth2 ](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry)authorization method, where the access token expires after a month. A refresh token is used to generate a new access token after it expires. This won't have any impact on current integrations if implemented properly. This authorization enables third-party applications (clients) to gain delegated access to protected resources in CleverReach via an API. When you set up an integration, you need to allow Integry to access your CleverReach account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in CleverReach are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to CleverReach every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which CleverReach acts as a trigger application) and perform an action in CleverReach, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are the following limitations of the CleverReach App Connector:

* Open tracking is only available for HTML-type campaigns.
* The 'Google Campaign Name' field works only if the 'Link Tracking Type' is 'Google.'


# ClickUp

[ClickUp](https://www.integry.io/apps/clickup) is a productivity platform that helps make management, communication, and collaboration smooth and simple with its built-in tools. You can use it to create custom workflows, communicate effectively through assigned comments, and work on multiple tasks through the multitask toolbar. It offers a tree structure view of your tasks. You can also customize the interface according to your needs. The ClickUp App Connector syncs and manages tasks with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your ClickUp account with Integry, here are a few things you need to learn about the ClickUp App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

ClickUp uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry/#scopes) authorization type. The end-user logs in and grants access to their ClickUp account. The ClickUp API notifies Integry that the end-user has given access to their account. Integry is then able to communicate with ClickUp's API on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in ClickUp are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to ClickUp every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which ClickUp acts as a trigger application) and perform an action in ClickUp, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations of the ClickUp App Connector.


# ClickSend

[ClickSend](https://www.integry.io/apps/clicksend) is a cloud-based service that lets you send and receive SMS, Email, Voice, Fax, and Letters worldwide. The app provides integratable products necessary for business communications. You can use their dashboard or APIs to send across rich media. The ClickSend App Connector helps you sync and manage contacts and campaigns with other third-party apps.‍

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your ClickSend account with Integry, here are a few things you need to learn about the ClickSend App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

ClickSend uses [API key + secret ](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry)authorization type. The end-user is identified by an API key and secret. Integry uses this information to perform an API request to ClickSend on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in ClickSend are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to ClickSend every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which ClickSend acts as a trigger application) and perform an action in ClickSend, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there is only one limitation of the ClickSend App Connector, there is no trigger to fetch updates in the campaign.


# Cliengo

[Cliengo](https://www.integry.io/apps/cliengo) is an online platform that interacts with your visitors and converts them to leads. Cliengo acts as a chat box for your company that helps you produce more sales. You can use it to save the data of the visitor with the chat box. Cliengo has a built-in CRM to make adding leads easy. It helps in escalating business processes by automation and also in generating reports. The Cliengo App Connector syncs and manages contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Cliengo account with Integry, here are a few things you need to learn about the Cliengo App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Cliengo uses the [API key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method. An API key identifies the end-user, and Integry uses this key to communicate with Cliengo's API on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Cliengo triggers are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Cliengo every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. When you set up an integration (in which Cliengo acts as a trigger application) and perform an action in Cliengo, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations of the Cliengo App Connector.<br>


# Coda

[Coda ](https://www.integry.io/apps/coda)is a tool that combines features of documents, spreadsheets, databases, notes, and project management tools. It enables you to collaborate with your team and populate your documents with text and infographics. You can use it to add text, reports, graphs, invoices, etc., and organize them into folders. It has adaptive views to enable your team or manager to work off the same data. The Coda App Connector syncs and manages documents with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Coda account with Integry, here are a few things you need to learn about the Coda App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Coda uses the [API key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method. An API key identifies the end-user, and Integry uses this key to communicate with Coda's API on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Coda triggers are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Coda every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. When you set up an integration (in which Coda acts as a trigger application) and perform an action in Coda, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

The documents can not be updated through the API.


# Constant Contact

[Constant Contact](https://www.integry.io/apps/constant-contact) is an online tool for email marketing. This platform can be used to create and manage campaigns and templates for email marketing, strengthen customer relations, and grow your contact lists. It enables you to create segmented customer lists and keep track of the sent emails. The Constant Contact App Connector helps you manage and sync contacts and email campaigns with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Constant Contact account with Integry, you can go through some basic specifications of the Constant Contact App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Constant Contact uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The access token expires in 24 hours and gets refreshed automatically after expiration.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in Constant Contact are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Constant Contact every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Hubspot acts as a trigger application) and perform an action in Constant Contact, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

At present, there is only one limitation of the Constant Contact App Connector that while updating an email campaign, only the name can be updated.


# ConvertKit

[ConvertKit](https://www.integry.io/apps?Search=meister) is an email marketing software with features for creators. It helps you grow your email list through vibrant forms, trackable data, and automations. You can schedule targeted content for your subscribers and build personalized automated emails through the sequence builder and define rules with workflows. ConvertKit supports subscriber segmentation through tags. ConvertKit syncs and manages subscribers with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your ConvertKit account with Integry, here are a few things you need to learn about the ConvertKit App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The authorization type used in ConvertKit is [API Secret](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry), where you have to provide just the API secret to authorize your account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

ConvertKit uses [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to ConvertKit every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which ConvertKit acts as a trigger application) and perform an action in ConvertKit, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations of the ConvertKit App Connector.


# Copper

[Copper](https://www.integry.io/apps/copper) is an online platform with email and marketing tools that save personal information to help boost your sales. It helps in organizing contacts, automating tasks, tracking your deals, managing projects, and getting reports. The Copper App Connector manages and syncs company, opportunity, task, and person with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Copper App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Copper uses the [API key + secret](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method. You must obtain a unique API key and App ID to get started, which can be requested in your Account's settings.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Copper uses[ poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to Copper every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Copper acts as a trigger application) and perform an action in Copper, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations for this App Connector.


# Customer.io

[Customer.io](http://customer.io/) enables users to send newsletters to selected segments of customers using their website data. It provides segmentation based on the activity of your website visitors so that you can generate personalized messages. It creates profiles of every sign-up based on on-site and in-app behavior. You can use it to keep a record of all emails and messages sent to users and track the usage trends of your app. The Customer.io App Connector syncs and manages customers and events with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Customer.io account with Integry, here are a few things you need to learn about the Customer.io App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The authorization type configured for this connector is [basic](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry). The basic auth type usually asks for your username and password and authenticates using those.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

There are no published triggers yet for the Customer.io App Connector.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations of the Customer.io App Connector.


# Delighted

[Delighted](https://delighted.com/) is an online platform using Net Promoter Score to gather real customer feedback through customized surveys. You can use it to create targeted surveys, send SMS or analyze feedback through your website. This customizable platform adapts according to your brand and customers. It offers several surveys that allow you to gather a large amount of data. The Delighted App Connector syncs and manages people with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Delighted account with Integry, here are a few things you need to learn about the Delighted App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Delighted uses the [basic](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The basic auth type usually asks for your username and password and authenticates using those. If anything else is needed, we add the details for it in the auth popup.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers used here are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Delighted every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Delighted acts as a trigger application) and perform an action in Delighted, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are no limitations of the Delighted App Connector.


# Demio

[Demio](https://www.demio.com/) is an online webinar platform. You can use it to let your audience attend a webinar using their browser or app. Demio also helps to customize the webinar material, registration forms, and presentations according to your brand. Demio also enables HD-quality streaming, sharing screens or webcams, and having public or private chats with your audience. The Demio App Connector syncs and manages registrations with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Demio account with Integry, here are a few things you need to learn about the Demio App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The authorization type is [API key + secret](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry). An API key and secret identify the end-user, and Integry uses this key to communicate with Demio's API on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

No triggers are implemented in Demio App Connector.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are no limitations of the Demio App Connector.


# Drip

[Drip](https://www.drip.com/) is an Ecommerce CRM that offers email marketing automation. You can have customer interactions that have a greater impact. It enables you to provide a personalized user experience to your customers and make the best decisions based on insights and data. You can also automate your workflows, create engaging content and roll out personalized emails for each customer with the help of Drip. It also offers customer segmentation based on actions. App Connector helps you sync and manage People with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Drip account with Integry, here are a few things you need to learn about the Drip App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Drip uses the [OAuth2.0](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The access token is long-lived, which means it will be generated only once and never expire.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers used are [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). Integry will receive the trigger instantly as soon as an event occurs in Drip.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

So far, there are no limitations of the Drip App Connector.


# E-goi

[E-goi](https://www.integry.io/apps/e-goi) is an online tool for Marketing Automation that any company can use to manage its entire sales cycle, from capturing leads to customer conversion and loyalty. With E-goi schedule, you can create landing pages, forms, and pop-ups, perform advanced automation, and implement an E-mail marketing strategy, SMS, WebPush, Push Notification, and Voice campaigns. You can also do behavioral and intention tracking on web pages and online stores and have a public API. The E-goi App Connector helps to sync and manage e-mail campaigns, emails, and SMs with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your E-goi account with Integry, here are a few things you need to learn about the E-goi App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

E-goi uses [API key-based](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. An API key identifies the end-user. An API key identifies the end-user, and Integry uses this key to communicate with E-goi's API on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in E-goi are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to E-goi every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which E-goi acts as a trigger application) and perform an action in E-goi, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Presently, there are the following limitations of the E-goi App Connector:

* The 'Subject' and 'HTML Body' fields are only for HTML type e-mail campaigns.
* The 'Webpage URL' field and 'Use Webpage Title as Subject' checkboxes are only for Webpage type e-mail campaigns.


# Eventbrite

[Eventbrite](https://www.integry.io/apps/eventbrite) is an event management and ticketing website. It is used to search and manage all types of local events. With this tool, you can find or create an event in your area. It also allows you to manage a secure event ticketing process and analytics. The Eventbrite App Connector enables you to automatically sync the events created or tickets purchased with any other third-party app. &#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Eventbrite account with Integry, you can go through some specifications of the Eventbrite App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Eventbrite uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method in which the access token doesn't expire. When you set up an integration, you need to log in and allow Integry to access your Eventbrite account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Eventbrite uses [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/) triggers for Event and Ticket objects. Therefore, as soon as an event occurs, Integry will receive the trigger instantly.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Here are some of the limitations of the Eventbrite App Connector.

* An event's start and end time fields only accept time in UTC Format: YYYY-MM-DD hh:mm:ss.
* The timezones in events should be in Area/City timezone Format, which can be found [here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones).
* Events with passwords cannot be marked as listed.
* The currency field accepts only the ISO 4217 currency code, which can be found [here](https://en.wikipedia.org/wiki/ISO_4217).


# EverAction

[EveryAction](https://www.integry.io/apps/everyaction) is a CRM that handles fundraising, donor management, and advocacy. It helps you segment and manage fundraising data, volunteers, and donors. You can effectively manage your campaigns through features such as integration with social networks, one-click donations, and better event management. It also helps with marketing automation, predictive analysis, and membership management. EveryAction App Connector syncs and manages contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your EveryAction account with Integry, here are a few things you need to learn about the EveryAction App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

EveryAction uses the [Basic](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. This authorization type asks for your username and password and authenticates using those.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The EveryAction connector used [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to EveryAction every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which EveryAction acts as a trigger application) and perform an action in EveryAction, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Presently, there are no limitations of the EveryAction App Connector.


# Everhour

[Everhour](https://www.integry.io/apps/everhour) is a time tracking and expense management software equipped with budgeting, forward resource planning, expense tracking, dashboards, and reports. You can use it to budget and track your projects, identify the resources and distribute them optimally amongst team members, track your time and tasks, create invoices from the time entries, and send them to your clients. It also helps your end-users create flexible reports of their projects. It integrates with several apps so that you can track time inside the app. The Everhour App Connector syncs and manages projects with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Everhour account with Integry, here are a few things you need to learn about the Everhour App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Everhour uses the [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. An API key identifies the end-user, and Integry uses this key to perform an API communication with Everhour on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Everhour uses [webhook-based](https://support.integry.io/hc/en-us/articles/360021913434-Creating-Webhook-Triggers) triggers. Therefore, Integry will receive the trigger instantly as soon as an event occurs.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Presently, there are no limitations of the Everhour App Connector.


# Formstack

[Formstack](http://www.formstack.com/) is an online data management solution that helps users collect information through various types of online forms, including surveys, job applications, event registrations, and payment forms. You can use it to create responsive forms, customize them through easy drag and drop, and integrate them in minutes. The forms can be created from scratch, or via pre-built templates. Formstack is extremely secure and can help in online payments as well. The Formstack App Connector syncs and manages forms with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Formstack account with Integry, here are a few things you need to learn about the Formstack App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The authorization type in Formstack is [OAuth 2](https://support.integry.io/hc/en-us/articles/11112617800985-Supported-Authentication-Types).&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The *form created* and form updated triggers in Front are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). which means Integry will send a request to Front every 5 minutes to collect data for contact triggers. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Front acts as a trigger application) and perform an action in Front, expect a 5-minute delay for the trigger to be received at Integry.The *new submission added* trigger is [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). Therefore, as soon as an event occurs, Integry will receive the trigger instantly.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are no limitations of the Formstack App Connector.


# Freshdesk

[Freshdesk](http://www.freshdesk.com/) is an online cloud-based customer service software providing helpdesk support with smart automations. It streamlines customer conversations across channels like email, social media, phone, and chat. The Freshdesk App Connector manages and syncs contact, company, and ticket with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Freshdesk account with Integry, here are a few things you need to learn about the Freshdesk App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Freshdesk uses the [APIKey+URL](https://support.integry.io/hc/en-us/articles/360022115853-Authentication-Types-Supported-in-Integry) authorization. An API key +URL identifies the end-user, and Integry uses this key+URL combination to communicate with Freshdesk's API on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The contact triggers are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/), which means Integry will send a request to Freshdesk every 5 minutes to collect data for contact triggers. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Freshdesk acts as a trigger application) and perform an action in Freshdesk, expect a 5-minute delay for the trigger to be received at Integry.The ticket trigger is [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). Therefore, as soon as an event occurs, Integry will receive the trigger instantly.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Presently, there are no limitations of the Freshdesk App Connector.


# Freshworks CRM

[Freshworks CRM](https://www.freshworks.com/crm/) is an online platform to get leads, boost customer engagement, drive deals to closure, and nurture existing customers. You can use it to view your customer’s interactions and automate your tasks. It also provides customized infographics to the user. The Freshworks App Connector manages and syncs contacts with other third-party apps.

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Freshworks account with Integry, here are a few things you need to learn about the Freshworks App Connector.

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Freshworks uses [API key+URL](https://support.integry.io/hc/en-us/articles/360022115853-Authentication-Types-Supported-in-Integry) authorization type. The API key and URL identify the end-user, and Integry uses this key to perform an API communication with Freshworks on behalf of that end-user.

You can find the above at Avatar > Settings > API Settings. Provide the API key as API Key and Bundle alias as URL.

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers used are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Freshworks every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Freshworks acts as a trigger application) and perform an action in Freshworks, expect a 5-minute delay for the trigger to be received at Integry.

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Presently, there are no limitations of the Freshworks App Connector.


# Mautic

Integry supports the flowing actions of Mautic.

#### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**     | **Method** | **Description**           |
| ------------ | ---------- | ------------------------- |
| Create Email | POST       | Creates a new email       |
| Update Email | PATCH      | Updates an existing email |

For more, please see [Mautic API docs](https://developer.mautic.org/).

#### Authorization <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Mautic uses [Basic with URL](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The end-user is identified through a combination of basic authentication (username and password) and a specific URL. Integry uses these credentials to perform API requests to Mautic on behalf of the end-user.

&#x20;

#### FAQs <a href="#id-01hw60a621etfhwyaqdtv9jkj2" id="id-01hw60a621etfhwyaqdtv9jkj2"></a>

**Why was my campaign created, but there was no HTML inside it?**\
This issue occasionally occurs due to a problem with the Mautic API. Since this is a problem on Mautic's end, there's not much we can do to resolve it directly. However, this issue is rare, and retrying after some time usually resolves it. We have reported this problem to Mautic for further investigation.


# Customer.guru

[Customer.guru](http://customer.guru/) is a tool for tracking customer satisfaction using Net Promoter Score (NPS). You can use this to analyze your customers in different segments based on what they ordered when they ordered, and how many orders they have placed. Customer.guru generates reports and lets you closely analyze customer data and activities. You can also create simple and customized surveys and use its follow-up features to achieve a higher response rate. The Customer.guru App Connector syncs and manages surveys with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Customer.guru account with Integry, here are a few things you need to learn about the Customer.guru App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The authorization type configured for this connector is [basic](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry). The basic auth type usually asks for your username and password and authenticates using those.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

No triggers are implemented in the Customer.guru App Connector.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are no limitations of this App Connector.


# Front

[Front](https://app.frontapp.com/) lets you manage all of your communication channels' emails, social media, chat, and SMS in one place. You can manage your private and shared conversations from anywhere with mobile apps. It helps you assign every conversation for clear ownership, coordinate the next steps with in-line comments and mentions, and avoid duplicate replies through collision detection. You can also use the inbuilt reminders feature. The Front App Connector syncs and manages contacts, messages, and tags with other third-party apps.

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Front account with Integry, here are a few things you need to learn about the Front App Connector.

&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Front uses [API key ](https://support.integry.io/hc/en-us/articles/11112617800985-Supported-Authentication-Types)based authorization. An API key identifies the end-user, and Integry uses this key to communicate with Front's API on behalf of that end-user.

&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in Front are[ poll-based.](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) Integry will send a request to Front every 5 minutes to collect data for contact triggers. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Front acts as a trigger application) and perform an action in Front, expect a 5-minute delay for the trigger to be received at Integry.

&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are no limitations of the Front App Connector.


# FTP

FTP is a standard network protocol provided by TCP/IP that can be used for transmitting files between hosts over the internet. You can use it to keep the data from your files synced between a remote computer and any app. You can also use it to access a remote computer that isn't a dedicated server with credentials like IP address, username, password, and optionally a port. Using FTP, you can sync the data on any online app with files like Text and CSV on a remote computer. This integration will keep reading your file periodically to keep the data up-to-date. The FTP App Connector can be used to make a connection with the FTP server.

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your FTP account with Integry, here are a few things you need to learn about the FTP App Connector.

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The authorization type is [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry). The API key identifies the end-user, and Integry uses this key to perform an API communication with FTP on behalf of that end-user.

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The trigger is [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). Therefore, as soon as an event occurs, Integry will receive the trigger instantly.

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are no limitations of the FTP App Connector.


# GetResponse

[GetResponse](https://www.integry.io/apps/getresponse) is an email marketing platform. You can use it to send email newsletters, campaigns, online surveys, and follow-up on autoresponders. You can also create personalized journeys for your customers based on their requirements, needs, data, etc. You can use the built-in templates for emails and campaigns. The GetResponse App Connector can help you manage and sync contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your GetResponse account with Integry, here are a few things you need to learn about the GetResponse App Connector.&#x20;

#### **Authorization Type** <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

GetResponse uses an [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) based authentication. The end-user is identified by an API key, and Integry uses this key to perform an API request to GetResponse on behalf of that end-user.&#x20;

#### **Triggers** <a href="#triggers-0-2" id="triggers-0-2"></a>

Triggers in GetResponse are [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). Therefore, Integry will receive the trigger instantly as soon as an event occurs.&#x20;

### **Limitations** <a href="#limitations-0-3" id="limitations-0-3"></a>

Presently, there are the following limitations of the GetResponse App Connector:

* The action *create contact* will take a few minutes to reflect in the GetResponse UI as it first gets added to a queue and then processed. If it still does not appear in the UI then that means the contact was rejected at some later stage.
* Campaigns can only be created or updated by adding or updating just the name field.


# GitHub

[GitHub](https://www.integry.io/apps/github) is an online platform for your users to manage and review code, collaborate, and manage private and open-source software. You can use it to not only organize your teams but also monitor your projects and their milestones. The features like issues, commits, rollbacks, etc. It helps keep all your team members synchronized across a project. The GitHub App Connector manages and syncs issues with other third-party apps.&#x20;

### Specifications <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your GitHub account with Integry, here are a few things you need to learn about the GitHub App Connector. **Authorization**GitHub uses [OAuth2.0](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) based authentication. The access token does expire as we support long-lived access tokens **Triggers**Triggers in GitHub are [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). Therefore, Integry will receive the trigger instantly as soon as an event occurs.&#x20;

### Limitations <a href="#limitations-0-1" id="limitations-0-1"></a>

There are no limitations of the GitHub App Connector as of now.


# Google Contacts

[Google Contacts](https://contacts.google.com/) is an online platform that allows you to manage your contacts and keep track of all your conversations. You can use it to manage all your contacts online in one place, review your recent conversations and create notes about your contacts. It also lets you save the details of contacts that you email the most. The Google Contacts App Connector syncs and manages contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Google Contacts account with Integry, here are a few things you need to learn about the Google Contacts App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Google Contacts uses the [OAuth ](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry)authorization type.The auth token expires after 1 hour and a new token is generated via refresh token.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

It uses [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to Google Contacts every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Google Contacts acts as a trigger application) and perform an action in Google Contacts, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Following are the limitations of the Google Contacts App Connector. User's refresh token will stop working when:

1. The user has revoked your app's access (ref:<https://support.google.com/accounts/answer/3466521#remove-access>)
2. The refresh token has not been used for six months.
3. The user account has exceeded the maximum number of granted (live) refresh tokens. The limit is 100 live refresh tokens. After the 101 is added, it will revoke the first refresh token


# Google Sheets

[Google Sheets](https://sheets.google.com/) is a file and data management tool that manages your data, and sheets and lets you collaborate with your team in real-time. You can use its in-built formulae and charts to perform data analysis. It can be used to keep an eye on trends and stats with charts, pivot tables, and other data filters. Your data and sheets stay synchronized across all platforms, so you are up-to-date across all your devices. The Google Sheets App Connector manages and syncs rows with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Google Sheets account with Integry, here are a few things you need to learn about the Google Sheets App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Google Sheets uses the [OAuth ](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry)authorization type. The auth token expires after 1 hour and a new token is generated via refresh token.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

It uses [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to Google Sheets every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Google Sheets acts as a trigger application) and perform an action in Google Sheets, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Following are the limitations of the Google Contacts App Connector.The user's refresh token will stop working when:

1. The user has revoked your app's access (ref:<https://support.google.com/accounts/answer/3466521#remove-access>)
2. The refresh token has not been used for six months.
3. The user account has exceeded the maximum number of granted (live) refresh tokens. The limit is 100 live refresh tokens. After the 101st token is added, it will revoke the first refresh token.


# GoToTraining

[GoToTraining](https://www.goto.com/training) is a web-hosted online training service. It offers online classroom and desktop sharing via the Internet in real time. It allows the desktop view of a host computer to be broadcast to a group of computers connected to the host through the Internet. You can use it to provide online training to your end-users on any device. It helps you manage online course catalogs, registration forms, and study material and accept payments. All the transmissions are protected with high-security encryption and passed through highly restrictive firewalls. The GoToTraining App Connector helps sync and manage trainings with other third-party apps.Specifications Before you connect your GoToTraining account with Integry, here are a few things you need to learn about the GotToTraining App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-0" id="authorization-type-0-0"></a>

GoToTraining uses the [OAuth2](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) based authorization method. The access token expires in 24 hours. It is automatically refreshed through a refresh token when it expires.&#x20;

#### Trigger Type <a href="#trigger-type-0-1" id="trigger-type-0-1"></a>

No triggers were implemented in the GoToTraining App Connector.&#x20;

### Limitations <a href="#limitations-0-2" id="limitations-0-2"></a>

There are no limitations of the GoToTraining App Connector.


# Groove

[Groove](https://www.groovehq.com/) is an all-in-one sales solution that gives you a knowledge base. It enables you to respond to your customers' tickets without any hassle. You can also use it to convert your email inbox into your team's customer service help desk. Groove comes with a customizable contact widget, which lets you embed contact forms to your website. The Groove App Connector syncs and manages tickets with other third-party apps.

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Groove connector.

#### Authorization Type <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The authorization type is [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry). The API key identifies the end-user, and Integry uses this key to perform an API communication with Groove on behalf of that end-user.

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in Groove are [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). Therefore, as soon as an event occurs, Integry will receive the trigger instantly.

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Presently, there are no limitations of the Groove App Connector.


# Help Scout

[Help Scout](https://www.helpscout.com/) is an email-based customer support platform. It helps you make personalized communications, create multiple mailboxes for a shared email address, get real-time information on who is viewing or replying, save time by using saved messages, create workflows, and save time and effort by automating repeated tasks. You can use it to get feedback from your customers, evaluate team performance, and track trends through automatically generated reports. The Help Scout App Connector syncs and manages articles and conversations with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Help Scout account with Integry, here are a few things you need to learn about the Help Scout App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The authorization type is [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry). The access token expires in 48 hours, and the refresh token is implemented. A new access token is generated with the help of the refresh token.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers of HelpScout are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Help Scout every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Help Scout acts as a trigger application) and perform an action in Help Scout, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

In the Article Object, the Keyword field needs comma-separated values, e.g., Value1, Value2.


# HubSpot

Integry supports a number of triggers and actions of HubSpot.

#### Triggers <a href="#h_01hr556ap5m0d97s0v2hv9bk41" id="h_01hr556ap5m0d97s0v2hv9bk41"></a>

| **Name**                  | **Type** | **Description**                                                   |
| ------------------------- | -------- | ----------------------------------------------------------------- |
| Contact Updated in a List | Polling  | Triggers when an existing contact is updated in a list            |
| Contact Added to a List   | Polling  | Triggers when a contact is added to a list                        |
| Contact Created           | Instant  | Triggers when a new contact is created                            |
| Contact Created/Updated   | Polling  | Triggers when a contact is created or updated                     |
| Quote Created/Updated     | Polling  | Triggers when a new quote is created or existing quote is updated |

For more, please see [Hubspot API docs](https://developers.hubspot.com/docs/api/webhooks). If you're not sure how triggers work in Integry, go [here](https://docs.integry.ai/hc/en-us/articles/29484874325017).

#### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**                 | **Method** | **Description**                                          |
| ------------------------ | ---------- | -------------------------------------------------------- |
| Delete Contact           | DELETE     | Deletes an existing contact                              |
| Unsubscribe Contact      | PATCH      | Unsubscribes a contact from all emails                   |
| Create Email Template    | POST       | Creates a new email template                             |
| Get Contact              | GET        | Fetches the details of a contact                         |
| Create Contact           | POST       | Creates a new contact                                    |
| Update Contact           | PATCH      | Updates an existing contact                              |
| Update Email Template    | PATCH      | Updates an existing email template                       |
| Bulk Contact Create      | POST       | Create contacts in bulk inside your account              |
| Bulk List Addition       | POST       | Add contacts into a list in bulk                         |
| Create Deal              | POST       | Creates a new deal                                       |
| Upsert Contact           | POST       | Creates a new HubSpot contact or updates an existing one |
| Remove Contact from List | POST       | Removes contact from list                                |
| Create Note Engagement   | POST       | Creates a new note engagement                            |
| Get Lifecycle Stages     | GET        | Fetches lifecycle stages of a contact                    |
| Search Company           | POST       | Searches a company by search criteria                    |
| Update Deal              | PATCH      | Updates an existing deal                                 |
| Delete Deal              | DELETE     | Deletes an existing deal                                 |
| Get Deal                 | GET        | Fetches a specific deal by ID                            |
| Create Quote             | POST       | Creates a new quote                                      |
| Create Line Item         | POST       | Creates a new line item                                  |
| Get Quote Details        | GET        | Fetches details of a quote                               |
| Get Line Item Details    | GET        | Fetches details of a line item                           |
| Batch Read Line Items    | POST       | Reads a batch of line items                              |
| Get Quote                | GET        | Fetches details of a quote                               |

For more, please see [Hubspot API docs](https://developers.hubspot.com/docs/api/crm/contacts#endpoint?spec=POST-/crm/v3/objects/contacts).

#### Authorization <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Your users will login to Hubspot via OAuth 2.0 using Integry's developer app. You can [replace it](https://docs.integry.ai/hc/en-us/articles/10887314172441) by [setting up your own](https://developers.hubspot.com/docs/api/oauth-quickstart-guide).<br>


# Keap

[Keap](https://keap.com/) is an automated email marketing and sales platform to deliver personalized service to clients. Keap includes products to manage customers, customer relationships, marketing, and e-commerce. You can use it to collect leads, write emails and texts, send emails to segmented lists, and carry out auto follow-ups. The Keap App Connector syncs and manages contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Keap account with Integry, here are a few things you need to learn about the Keap App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The Keap App Connector uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The access token is valid for 24 hours. After the expiration, a new access token is generated using a refresh token which is valid for 45 days.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers used in Keap are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Keap every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Keap acts as a trigger application) and perform an action in Keap, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

The following are the limitations of the Keap App Connector:

* In the contact object, the country field only accepts ISO-based codes, e.g., PAK or AUS.
* In the contact object, the birthday and anniversary fields only accept dates in YYYY-MM-DD format.


# Mailchimp Transactional

[Mailchimp Transactional](https://www.integry.io/apps/mailchimp-transactional) is a tool to send transactional emails (password resets, order placement, welcome messages) triggered by user actions, personalized 1:1 messages, and targeted e-commerce emails. This app, also known as Mandrill, is a platform for email marketing automation and can be used to send event-driven messages to your customers. You can also use it to design one-to-one personalized e-commerce emails. The Mailchimp Transactional App Connector syncs and manages templates and emails with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Mailchimp Transactional account with Integry, here are a few things you need to learn about the Mailchimp Transactional App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

In order to use Rest APIs, users need to authenticate via [API key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry). Users can [generate](https://mailchimp.com/developer/transactional/guides/quick-start/#generate-your-api-key) a new [API key](https://mandrillapp.com/settings) from the Mandrill App. The API key is included in the request body. Integry uses the API key to identify users.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Mailchimp Transactional supports [Webhook-based](https://support.integry.io/hc/en-us/articles/360021913434-Creating-Webhook-Triggers) triggers for specific topics. Therefore, as soon as an event occurs, Integry will receive the trigger instantly.

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Presently, there are the following limitations of the Mailchimp Transactional App Connector:

* Sorting is not supported; thus, poll-based triggers cannot be implemented.
* Pagination is also not supported, so we cannot implement either queries or custom-sort.
* Only the following events are supported by Webhooks:
  * Message Is Sent
  * Message Is Delivered
  * Message Is Delayed
  * Message Is Bounced
  * Message Is Soft-Bounced
  * Message Is Opened
  * Message Is Clicked
  * Message Is Marked As Spam
  * Message Recipient Unsubscribes
  * Message Is Rejected
  * Rejection Denylist Changes
  * Rejection Allowlist Changes

<br>


# Mailjet

[Mailjet](https://www.integry.io/apps/mailjet) is a cloud-based email delivery and tracking system which allows users to send marketing and transactional emails. The app is easy-to-use and enables you to design and send out automated email marketing campaigns and newsletters. The Mailjet App Connector can be used to manage and sync campaigns, contacts, and contact lists with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Mailjet App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Mailjet uses [API Key+secret](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) type authorization. The end-user is identified by an API key+secret, and Integry uses this key to perform an API request to Mailjet on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

[Poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers are used in Mailjet. Integry will send a request to Mailet every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Mailjet acts as a trigger application) and perform an action in Mailjet, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations of the Mailjet App Connector.


# MailUp

[MailUp](https://www.integry.io/apps/mailup) is an easy-to-use platform for building customizable marketing campaigns through email, SMS, and other messaging apps. Many multinational, small, and medium businesses use MailUp to promote products and services. The MailUp App Connector helps you manage and sync email, email recipient, SMS, and SMS recipient with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your MailUp account with Integry, here are a few things you need to learn about the MailUp App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

MailUp uses [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The access token expires in 1 hour and gets refreshed automatically after expiration.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in MailUp are [poll-based](https://support.integry.io/hc/en-us/articles/360021913374-Creating-Poll-Based-Triggers). Integry will send a request to MailUp every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which MailUp acts as a trigger application) and perform an action in MailUp, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

No triggers exist to check for any update of Email, SMS, and Recipient.


# MeisterTask

[MeisterTask](https://www.integry.io/apps/meistertask) is an online multi-platform collaboration and project management tool. You can use it to organize and manage tasks in a customizable environment that perfectly adapts to your workflow and automates recurring steps. It can be used to assign tasks to your team members, implement your ideas, and plan and visualize your tasks. It helps you communicate efficiently and save all your activities in the task's activity stream for traceability in the future. The MeisterTask App Connector syncs and manages projects with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your MeisterTask account with Integry, here are a few things you need to learn about the MeisterTask App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

MeisterTask uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The access token does not expire and hence does not need to be regenerated.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The app uses [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to MeisterTask every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which MeisterTask acts as a trigger application) and perform an action in MeisterTask, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are no limitations of the MeisterTask App Connector.


# Monday.com

[Monday.com](https://www.integry.io/apps/monday-com) is an online tool to manage workload, track projects, and communicate with people. It also enables you to make lists of tasks and activities to be done and assign them to people in various teams. It helps in effectively managing work by adding comments, documents, and files to a task. The boards created by users automatically sync with Integry. The Monday.com App Connector manages and syncs tasks and projects with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Monday.com App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Monday.com uses [API key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) based authentication. The end-user is identified by an API key, and Integry uses this key to perform an API request to Monday.com on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Monday.com uses [poll-based](https://support.integry.io/hc/en-us/articles/360021913374-Creating-Poll-Based-Triggers) triggers. Integry will send a request to Monday.com every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Monday.com acts as a trigger application) and perform an action in Monday.com, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations for this App Connector.


# MoonMail

[MoonMail](https://moonmail.io/) is an online email marketing platform that allows you to draft and share newsletters. You can use its features, like email, voice, SMs, etc., to increase your sales and conversion rates. It provides automated email marketing with the ability to add new contacts or update existing ones. You can trigger your campaigns based on certain events. The MoonMail App Connector syncs and manages email templates with other third-party apps.

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your MoonMail account with Integry, here are a few things you need to learn about the MoonMail App Connector.

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

MoonMail uses the [API key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) based authorization. An API key identifies the end-user, and Integry uses this key to communicate with MoonMail's API on behalf of that end-user.

&#x20;Trigger Type

Presently, there are no triggers implemented for MoonMail.

### Limitations <a href="#limitations-0-2" id="limitations-0-2"></a>

Currently, there are the following limitations to the MoonMail App Connector:

* The longitude and latitude values in contact action need to be decimal.
* The country code in contact action mu


# Moosend

[Moosend](https://www.integry.io/apps/moosend) is a web-based marketing automation tool that helps you seamlessly manage your email campaigns, so you can grow your business. This email platform helps small and medium businesses to increase lead generation and nurture audience. The Moosend App Connector can be used to sync and manage campaigns and members with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Moosend account with Integry, you can go through some basic specifications of the Moosend App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The auth type used in Moosend is [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry). An API key identifies the end-user, and Integry uses this key to communicate with Moosend's API on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Moosend triggers are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Moosend every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. When you set up an integration (in which Moosend acts as a trigger application) and perform an action in Moosend, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

The Moosend app has the following limitations:

* While creating an A/B campaign you need to fill the Web location B field if the campaign type is content, Sender B if the campaign type is sender, and subject B if the content type is Subject Line respectively.
* A regular campaign cannot be updated to an A/B campaign and vice versa.


# Nimble

[Nimble ](https://www.integry.io/apps/nimble)is an online platform that combines high-end CRM systems and social media. You can use the dashboard available in Nimble to monitor the history of your customers. Nimble automatically syncs your data and brings your customers' data to one place. The Nimble CRM App Connector helps you manage and sync contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Nimble App Connector:&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Nimble CRM uses [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The end-user is identified by an API key, and Integry uses this key to perform an API request to Nimble CRM on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in Nimble are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Nimble every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Nimble acts as a trigger application) and perform an action in Nimble, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

This API is still under development and subject to change.


# Notion

[Notion](https://www.notion.so/) is a note-taking software platform that enables companies to collaborate and manage global remote teams on the same page. It helps members of companies or organizations manage their knowledge for greater efficiency and productivity. Their customers include Pixar, loom, Typeform, codeacademy, and Blinklist. The Notion App Connector syncs and manages pages and database items with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Notion connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Notion uses [OAuth ](https://support.integry.io/hc/en-us/articles/11112617800985-Supported-Authentication-Types)type authorization. The access token in Notion does not expire so token refresh is not needed.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Notion uses [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to Notion every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. When you set up an integration (in which Notion acts as a trigger application) and perform an action in Notion, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations of the Notion App Connector.


# Ontraport

[Ontraport](https://www.integry.io/apps/ontraport) is a sales, marketing, and business automation software for entrepreneurs, solopreneurs, and small businesses. It incorporates tools like CRM, marketing automation, ECommerce, and reporting. The contacts and products created in Ontraport automatically sync with Integry. The Ontraport App Connector manages and syncs contacts and products with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Ontraport account with Integry, you can go through some specifications of the Ontraport App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Ontraport uses the [API key + secret](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method. You must obtain a unique API key and App ID to get started, which can be requested in your [Administration settings](https://app.ontraport.com/#!/api_settings/listAll).&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Ontraport uses [Poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to Ontraport every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Ontraport acts as a trigger application) and perform an action in Ontraport, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Here are some of the limitations of the Ontraport Connector:

* The Product Updated, Campaign Update, and Contact Updated/Deleted Activities are not supported in the Ontraport App Connector.
* The Product object does not support custom fields.
* For date fields in Contact Object, you must map with a field that uses the YYYY-MM-DD format.
* Some objects (deals, companies, etc.) are not visible by default in your Ontraport account. You need to turn on the toggle button for these objects from the app's settings here:<https://app.ontraport.com/#!/app_marketplace/view>.


# PagerDuty

[PagerDuty ](https://www.integry.io/apps/pagerduty)is a powerful online platform for managing real-time digital operations. The PagerDuty App Connector helps you manage and sync any kind of incident that occurs with other third-party apps. For example, alter an account's configuration, pipe events from a monitoring tool into PagerDuty, or retrieve information about activity on a PagerDuty account.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the specifications of the PagerDuty App Connector:&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

PagerDuty uses the [OAuth ](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry)authorization type. The auth token can be used continuously to make requests until the end-user or app owner revokes it. When you set up an integration, you need to log in and allow Integry to access your PagerDuty account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

PagerDuty uses [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/) triggers. Therefore, as soon as an event occurs, Integry will receive the trigger instantly.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations of the PagerDuty App Connector.


# Pipedrive

[Pipedrive](https://www.integry.io/apps/pipedrive) is a cloud-based CRM that helps you prioritize deals, track performance, and predict revenue. The Pipedrive App Connector enables you to sync and manage people, deals, leads, activities, users, and organizations with other third-party app accounts.&#x20;

### Specifications <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Pipedrive account with Integry, you can go through some basic specifications of the Pipedrive App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Pipedrive uses an [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) for authorization. The end-user is identified by an API key, and Integry uses this key to perform an API request to Pipedrive on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Pipedrive uses [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/) triggers for deal, user, organization, and person objects. For these objects, as soon as an event occurs, Integry will receive the trigger right away.On the other hand, [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) trigger is used for the lead object. In this case, Integry will send a request to Pipedrive every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Pipedrive acts as a trigger application) and perform an action in Pipedrive, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Here are some of the limitations of the Pipedrive App Connector.

* While creating a lead, you must link it to at least one of the persons or one of the organizations. If none of them exist, then you need to create one.
* In leads, the expected closing date needs to be provided in ISO 8601 format: YYYY-MM-DD.
* A deal must always be linked to a person, organization, or both.
* The probability of deals will only be shown when deal property for the pipeline of the deal is enabled.
* Pipedrive has an authenticating rate limit according to your account, details of which are:
  1. **Essential**: 20 requests per 2 seconds per API token
  2. **Advanced**: 40 requests per 2 seconds per API token
  3. **Professional**: 80 requests per 2 seconds per API token
  4. **Enterprise**: 120 requests per 2 seconds per API token


# Pipeline

[Pipeline](https://www.integry.io/apps/pipeline) is an online platform to increase your sales productivity. It combines sales engagement and CRM in one user-friendly application. The platform enables you to use intuitive tools for integrations. The Pipeline App Connector can be used to make seamless integrations with other third-party app accounts to manage your deals, leads, and contacts.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Pipeline App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

The Pipeline app uses [API Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) based authentication. The end-user is identified by an API key, and Integry uses this key to perform an API request to Pipeline on behalf of that end-user. To use this authentication type for this app, you just need to grab your `api_key` and Allow Unregistered API from API Integrations, shown above.&#x20;

<figure><img src="/files/o8E4aIH9mXvhkp8VvDgq" alt=""><figcaption></figcaption></figure>

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The Pipeline triggers are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Pipeline every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. When you set up an integration (in which Pipeline acts as a trigger application) and perform an action in Pipeline, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

A specific date format is to be used in deals that is YYYY-MM-DD.


# Salesforce

Integry supports a number of triggers and actions of Salesforce.

#### Triggers <a href="#h_01hr556ap5m0d97s0v2hv9bk41" id="h_01hr556ap5m0d97s0v2hv9bk41"></a>

| **Name**            | **Type** | **Description**                                                                                         |
| ------------------- | -------- | ------------------------------------------------------------------------------------------------------- |
| Contact Created     | Polling  | Triggers when a contact is created                                                                      |
| Contact Updated     | Polling  | Triggers when a contact is updated                                                                      |
| Contact Deleted     | Polling  | Triggers when a contact is deleted                                                                      |
| Lead Created        | Polling  | Triggers when a lead is created                                                                         |
| Lead Updated        | Polling  | Triggers when a lead is updated                                                                         |
| Lead Deleted        | Polling  | Triggers when a lead is deleted                                                                         |
| Lead Merged         | Polling  | Triggers when a lead is merged into another lead and returns the lead that gets deleted after the merge |
| Task Created        | Polling  | Triggers when a new task is created                                                                     |
| Task Updated        | Polling  | Triggers when an existing task is updated                                                               |
| Task Deleted        | Polling  | Triggers when an existing task is deleted                                                               |
| Account Created     | Polling  | Triggers when a new account is created                                                                  |
| Account Updated     | Polling  | Triggers when an existing account is updated                                                            |
| Account Deleted     | Polling  | Triggers when an existing account is deleted                                                            |
| Opportunity Created | Polling  | Triggers when a new opportunity is created                                                              |
| Opportunity Updated | Polling  | Triggers when an existing opportunity is updated                                                        |
| Opportunity Deleted | Polling  | Triggers when an existing opportunity is deleted                                                        |
| Campaign Created    | Polling  | Triggers when a new campaign is created                                                                 |
| Campaign Updated    | Polling  | Triggers when an existing campaign is updated                                                           |
| Campaign Deleted    | Polling  | Triggers when an existing campaign is deleted                                                           |
| Product Created     | Polling  | Triggers when a new product is created                                                                  |
| Product Updated     | Polling  | Triggers when an existing product is updated                                                            |
| Order Created       | Polling  | Triggers when a new order is created                                                                    |
| Order Updated       | Polling  | Triggers when an existing order is updated                                                              |

&#x20;

For more, please see [Salesforce API docs](https://developer.salesforce.com/docs/apis). If you're not sure how triggers work in Integry, go [here](https://support.integry.io/hc/en-us/articles/29484874325017).

#### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**                                | **Method** | **Description**                                                      |
| --------------------------------------- | ---------- | -------------------------------------------------------------------- |
| Delete Contact                          | DELETE     | Deletes an existing contact                                          |
| Contact Opt In/Out of Email             | PATCH      | Opts a contact in or out of email services                           |
| Lead Opt In/Out of Email                | PATCH      | Opts a lead in or out of email services                              |
| Create Task                             | POST       | Creates a new task                                                   |
| Delete Task                             | DELETE     | Deletes an existing task                                             |
| Update Task                             | PATCH      | Updates an existing task                                             |
| Delete Opportunity                      | DELETE     | Deletes an existing opportunity                                      |
| Delete Account                          | DELETE     | Deletes an existing account                                          |
| Create Opportunity                      | POST       | Creates a new opportunity                                            |
| Update Opportunity                      | PATCH      | Updates an existing opportunity                                      |
| Create Account                          | POST       | Creates a new account                                                |
| Update Account                          | POST       | Updates an existing account                                          |
| Create Campaign                         | POST       | Creates a new campaign                                               |
| Update Campaign                         | PATCH      | Updates an existing campaign                                         |
| Create Product                          | POST       | Creates a new product                                                |
| Update Product                          | PATCH      | Updates an existing product                                          |
| Create Order                            | POST       | Creates a new order                                                  |
| Update Order                            | PATCH      | Updates an existing order                                            |
| Delete Lead                             | DELETE     | Deletes an existing lead                                             |
| Create Lead                             | POST       | Creates a new lead                                                   |
| Update Lead                             | PATCH      | Updates an existing lead                                             |
| Get All Lead Statuses                   | GET        | Fetches the list of all the lead statuses from your account          |
| Create User                             | POST       | Creates a new user in your Salesforce organization                   |
| Get Lead by ID                          | GET        | Fetches the details of a lead                                        |
| Get Contact by ID                       | GET        | Fetches the details of a contact                                     |
| Add Lead or Contact to Campaign Members | POST       | Adds the selected lead or contact to the selected campaign's members |
| Create Contact                          | POST       | Creates a new contact                                                |
| Update Contact                          | PATCH      | Updates an existing contact                                          |

For more, please see [Salesforce API docs](https://developer.salesforce.com/docs/apis).

#### Authorization <a href="#h_01hr556ap450c8s3d5hf8vc37f" id="h_01hr556ap450c8s3d5hf8vc37f"></a>

Your users will login to Salesforce via OAuth 2.0 using Integry's developer app. You can [replace it](https://support.integry.io/hc/en-us/articles/10887314172441) by [setting up your own](https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_oauth_and_connected_apps.htm).&#x20;

#### Limitations <a href="#id-01hw7xga6eebx1ryc0zn192pt8" id="id-01hw7xga6eebx1ryc0zn192pt8"></a>

Following are the limitations in the Salesforce App Connector as yet.

* Boolean type custom fields are not supported for field mapping.
* Sandbox environment is not supported for Flow testing.
* If you try to connect an account that is not API enabled, you won't be able to authenticate your account.&#x20;

#### FAQs <a href="#id-01hw60a621etfhwyaqdtv9jkj2" id="id-01hw60a621etfhwyaqdtv9jkj2"></a>

**What does the “OAUTH\_APP\_BLOCKED” error in Salesforce mean, and how can I resolve it?**\
The “OAUTH\_APP\_BLOCKED” error indicates that the app you are trying to access is blocked by an administrator. This can happen if the app's access has been restricted within the Salesforce CRM settings.

To resolve this issue, you need to check the “Connected Apps OAuth Usage” settings within an admin account and unblock the app. Follow these steps to do so:

1. Sign in to Salesforce CRM as an administrator.
2. Navigate to **Setup**.
3. Go to **Platform Tools > Apps > Connected Apps > Connected Apps OAuth Usage**.
4. Locate the app that is blocked.
5. Select **Unblock** for the app.

&#x20;

**What does the “INVALID\_SESSION\_ID” error in response mean in salesforce and how can I resolve it?**\
The “INVALID\_SESSION\_ID” error indicates that your access token has become invalid. This situation can occur for various reasons, such as the user revoking the app’s access or changes made to the user’s security settings.\
When this error occurs, it is necessary for you to re-authenticate in order to restore the integration’s functionality, simply trying to enable the integration again will result in the same error message.\
Here is an example of what the error payload will look like:

```json
[
    {
        "message": "Session expired or invalid",
        "errorCode": "INVALID_SESSION_ID"
    }
]
```

<br>


# SendPulse

[SendPulse ](https://www.integry.io/apps/sendpulse)is an online automation platform for business promotion and customer retention. It allows you to send email and SMS campaigns, work with clients using chatbots for Telegram, Facebook Messenger, WhatsApp, and Instagram, and create landing pages. The SendPulse App Connector helps sync and manage campaigns and mailing lists with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your SendPulse account with Integry, here are a few things you need to learn about the SendPulse App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

SendPulse uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method, where the access token expires after an hour. A refresh token is used to generate a new access token after it expires. This won't have any impact on existing integrations if implemented properly. This authorization enables third-party applications (clients) to gain delegated access to protected resources in SendPulse via an API. When you set up an integration, you need to allow Integry to access your SendPulse account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

SendPulse uses [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to SendPulse every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which SendPulse acts as a trigger application) and perform an action in SendPulse, expect a 5-minute delay to receive the trigger at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

SendPulse App Connector doesn't support the queries and triggers for **contact** and **deal** objects.


# Slack

[Slack](https://www.integry.io/apps/slack) is a secure online messaging app for your team to stay connected internally as well as with external teams. It also enables you to automate tasks inside and outside of Slack and organize communication using channels based on teams, clients, or projects. You can also share files and audio clips with your peers or even post a bot message. The Slack App Connector can be used to manage messages, channels, and user statuses between your Slack account and other third-party app accounts.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Slack account with Integry, you can go through some basic specifications of the Slack App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Slack uses an[ OAuth2](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) based authentication and stores two types of access tokens-user access token and bot token. These access tokens never expire. When setting up an integration, you need to allow Integry to request and acquire access to your Slack account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

No triggers are implemented as of now, but when we implement them, these will be [webhook based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). This means that as soon as an event occurs, Integry will receive the trigger right away.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Here are some of the limitations of the Slack App Connector:&#x20;

* No messages can be sent to DMs or Grouped DMs using the "Post Message" activity.
* As an end-user, you can only join a public channel using the "Join Channel" activity.
* Only fixed access tokens are supported. Fixed access tokens don't expire and hence a refresh token is not needed to generate a new one.


# Snappy

[Snappy](https://www.integry.io/apps/snappy) is an online email ticketing, knowledge base, and support widget for your growing customer base. It works like a helpdesk with a quick email ticketing system. It helps track performances using custom reports. You can also create your customer self-help through the built-in knowledge base. Snappy lets your end-users insert knowledge base articles in your tickets and merge, reply or tag to multiple tickets at once. The Snappy App Connector manages and syncs tickets with other third-party apps.

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Snappy account with Integry, here are a few things you need to learn about the Snappy App Connector.

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Snappy uses the [Basic](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The Basic auth type usually asks for your username and password and authenticates using those. If anything else is needed, we add the details for it in the auth popup.

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

It uses [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/) triggers. Integry will send a request to Snappy every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Snappy acts as a trigger application) and perform an action in Snappy, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Since the API does not support pagination, Import or Query is also not supported.


# SolarWinds

[SolarWinds](https://www.solarwinds.com/service-desk) is an enterprise service desk and IT asset-management provider. You can use it to manage, gather, prioritize tickets and gain insights into what issues are impacting your business without disturbing the flow of things. It also helps in executing change plans while formalizing documentation and approval processes. The SolarWinds App Connector syncs and manages incidents with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your SolarWinds account with Integry, here are a few things you need to learn about the SolarWinds App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

SolarWinds uses [API-Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization. An API key identifies the end-user, and Integry uses this key to communicate with SolarWinds's API on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers used in SolarWinds are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to SolarWinds every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. When you set up an integration (in which SolarWinds acts as a trigger application) and perform an action in SolarWinds, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

The date format for tasks or incidents should be (YYYY-MM-DD).


# Stripe

[Stripe](https://stripe.com/) is an online software that accepts payments, sends payouts, and manages businesses online.

It allows you to create websites and apps that send payouts and accept payments. It is extremely secure and helps you send invoices without fraud, have an easy checkout, manage your business spending, and issue virtual cards. The Stripe App Connector syncs and manages customers with other third-party apps.

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Following are the basic specifications of the Stripe connector.

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Stripe uses the [API key](https://support.integry.io/hc/en-us/articles/11112617800985-Supported-Authentication-Types) based authorization method. The API key identifies the end-user, and Integry uses this key to perform an API communication with Stripe on behalf of that end-user.

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The Stripe triggers are [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/). Therefore, as soon as an event occurs, Integry will receive the trigger instantly.

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are no limitations of the Stripe App Connector.


# SurveySparrow

[SurveySparrow](https://surveysparrow.com/) is an online survey tool. It has a dual-user interface that helps you create chat-like surveys or conversational forms. The features include previews, recurring surveys, customization, rich analytics, audience management, and more. You can use it to create market research forms, employee feedback, and customer satisfaction forms. The SurveySparrow App Connector syncs and manages contacts with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your SurveySparrow account with Integry, here are a few things you need to learn about the SurveySparrow App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

SurveySparrow uses the [API-Key](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization. An API key identifies the end-user, and Integry uses this key to communicate with SurveySparrow's API on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers used in SurveySparrow are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to SurveySparrow every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. When you set up an integration (in which SurveySparrow acts as a trigger application) and perform an action in SurveySparrow, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

There are no limitations of the SurveySparrow App Connector.


# Teamgate

[Teamgate ](https://www.integry.io/apps/teamgate)is a customer relationship management tool designed to increase your sales. It is easy to use and helps streamline the sales process by gathering leads and closing deals. The Teamgate App Connector helps you manage and sync contacts and leads with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Insightly account with Teamgate, you can go through some basic specifications of the Teamgate App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Teamgate uses [API Key + secret](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization type. The end-user is identified by an API key and a secret, and Integry uses this key+secret combination to perform API requests to Teamgate on behalf of that end-user.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in Teamgate are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Teamgate every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Teamgate acts as a trigger application) and perform an action in Teamgate, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations in the Teamgate App Connector.


# Unbounce

[Unbounce](https://www.integry.io/apps/unbounce) is an online platform that helps you engage with your target market by developing highly-optimized landing pages. You can design landing pages that convert your visitors into customers without writing a single line of code. Unbounce offers conversion-focused, industry-specific templates for landing pages. You can customize the templates by dragging and dropping design elements and adding custom images. Furthermore, Unbounce lets you publish SSL-encrypted landing pages. The Unbounce App Connector helps sync and manage leads with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Unbounce account with Integry, here are a few things you need to learn about the Unbounce App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Unbounce uses the [OAuth2](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method. The access token expires in 10 minutes and gets refreshed automatically after expiration.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The lead object has [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/) triggers. Therefore, Integry will receive the trigger instantly as soon as an event occurs.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there are no limitations of the Unbounce App Connector.


# Zoho Books

[Zoho Books](https://www.integry.io/apps/zoho-books) is a great online tool for bookkeeping your company's financial records and staying on top of business trends in the fintech world. It is also used as accounting software to manage your finances, automate your business workflows, track stock, and manage projects by helping you work jointly across departments. The Zoho Books App Connector enables you to sync all kinds of accounting entries between your Zoho Books account and other third-party app accounts.&#x20;

### Specifications <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Zoho Books account with Integry, here are a few things you need to learn about the Zoho Books App Connector.&#x20;

#### Authorization Type <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

&#x20;Zoho Books uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method where the access token expires after an hour. A refresh token is used to generate a new access token after it expires. This won't have any impact on current integrations if implemented properly. When you set up an integration, you need to allow Integry to access your Zoho Books account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

Zoho Books triggers are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Zoho Books every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. When you set up an integration (in which Zoho Books acts as a trigger application) and perform an action in Zoho Books, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

As of now, following are the limitations of the Zoho Books App Connector.&#x20;

* Only correct email addresses can be used to test this App Connector.
* The *Update* action for invoices and items only updates the created date and not the due date.
* While creating an invoice, the discount is only applicable when it is applied on the entity level.
* The discount should not exceed the invoice total.
* If the discount is applied on the item level, the 'discount before tax' checkbox must be checked while creating an invoice.
* At least one item must be selected to create an invoice.
* The stock keeping unit (SKU) of every item should be unique.
* We are only catering to US region, for now.


# Zoho Campaigns

[Zoho Campaigns](https://www.integry.io/apps/zoho-campaigns) is an online platform for email marketing. It helps in managing the email database of your leads and contacts. You can use it to create personalized emails and automated workflows and also build relations with potential customers. The Zoho Campaigns App Connector helps you sync and manage campaigns, topics, and contacts with other third-party apps.&#x20;

### ‍Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Zoho Campaigns account with Integry, here are a few things you need to learn about the Zoho Campaigns App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Zoho Campaigns uses the [OAuth ](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry)authorization method, where the access token expires after an hour. A refresh token is used to generate a new access token after it expires. This won't have any impact on current integrations if implemented properly. This authorization enables third-party applications (clients) to gain delegated access to protected resources in Zoho via an API. When you set up an integration, you need to allow Integry to access your Zoho Campaigns account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers in Zoho Campaigns are [poll-based](https://www.testpreptraining.com/tutorial/describe-polling-triggers-and-their-usage/). Integry will send a request to Zoho Campaigns every 5 minutes to collect data. In case of an occurrence of selected events, a trigger will be received at Integry with the required payload. Therefore, when you set up an integration (in which Zoho Campaigns acts as a trigger application) and perform an action in Zoho Campaigns, expect a 5-minute delay for the trigger to be received at Integry.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there is only one limitation of this app. The Zoho Campaigns connector does not support '**.cn**' domains.


# Zoho CRM

Integry supports a number of triggers and actions of Zoho CRM.

#### Triggers <a href="#h_01hr556ap5m0d97s0v2hv9bk41" id="h_01hr556ap5m0d97s0v2hv9bk41"></a>

| **Name**         | **Type** | **Description**                     |
| ---------------- | -------- | ----------------------------------- |
| Contact Created  | Polling  | Triggers when a contact is created  |
| Contact Updated  | Polling  | Triggers when a contact is updated  |
| Contact Deleted  | Polling  | Triggers when a contact is deleted  |
| Lead Created     | Polling  | Triggers when a lead is created     |
| Lead Updated     | Polling  | Triggers when a lead is updated     |
| Lead Deleted     | Polling  | Triggers when a lead is deleted     |
| Account Created  | Polling  | Triggers when an account is created |
| Account Updated  | Polling  | Triggers when an account is updated |
| Account Deleted  | Polling  | Triggers when an account is deleted |
| Task Created     | Polling  | Triggers when a task is created     |
| Task Updated     | Polling  | Triggers when a task is updated     |
| Task Deleted     | Polling  | Triggers when a task is deleted     |
| Deal Created     | Polling  | Triggers when a deal is created     |
| Deal Updated     | Polling  | Triggers when a deal is updated     |
| Deal Deleted     | Polling  | Triggers when a deal is deleted     |
| Meeting Created  | Polling  | Triggers when a meeting is created  |
| Meeting Updated  | Polling  | Triggers when a meeting is updated  |
| Meeting Deleted  | Polling  | Triggers when a meeting is deleted  |
| Campaign Created | Polling  | Triggers when a campaign is created |
| Campaign Updated | Polling  | Triggers when a campaign is updated |

For more, please see [Zoho API docs](https://www.zoho.com/crm/developer/docs/api/v3/). If you're not sure how triggers work in Integry, go [here](https://support.integry.io/hc/en-us/articles/29484874325017).

&#x20;

#### Actions <a href="#h_01hr56vpze824xf8dyw4e604x7" id="h_01hr56vpze824xf8dyw4e604x7"></a>

| **Name**                | **Method** | **Description**                                                     |
| ----------------------- | ---------- | ------------------------------------------------------------------- |
| Create Lead             | POST       | Creates a new lead                                                  |
| Update Lead             | PUT        | Updates an existing lead                                            |
| Delete Lead             | DELETE     | Deletes an existing lead                                            |
| Get Lead                | GET        | Fetches a specific lead by ID                                       |
| Search Leads            | GET        | Retrieves the latest 200 leads meeting the specified criteria       |
| Create Account          | POST       | Creates a new account                                               |
| Update Account          | PUT        | Updates an existing account                                         |
| Delete Account          | DELETE     | Deletes an existing account                                         |
| Get Account             | GET        | Fetches a specific account by ID                                    |
| Search Accounts         | GET        | Retrieves the latest 200 accounts meeting the specified criteria    |
| Create Task             | POST       | Creates a new task                                                  |
| Update Task             | PUT        | Updates an existing task                                            |
| Delete Task             | DELETE     | Deletes an existing task                                            |
| Get Task                | GET        | Fetches a specific task by ID                                       |
| Search Tasks            | GET        | Retrieves the latest 200 tasks fulfilling the specified criteria    |
| Create Meeting          | POST       | Creates a new meeting                                               |
| Update Meeting          | PUT        | Updates an existing meeting                                         |
| Delete Meeting          | DELETE     | Deletes an existing meeting                                         |
| Get Meeting             | GET        | Fetches a specific meeting by ID                                    |
| Search Meetings         | GET        | Retrieves the latest 200 meetings fulfilling the specified criteria |
| Create Deal             | POST       | Creates a new deal                                                  |
| Update Deal             | PUT        | Updates an existing deal                                            |
| Delete Deal             | DELETE     | Deletes an existing deal                                            |
| Get Deal                | GET        | Fetches a specific deal by ID                                       |
| Search Deals            | GET        | Retrieves the latest 200 deals meeting the specified criteria       |
| Create Campaign         | POST       | Creates a new campaign                                              |
| Update Campaign         | PUT        | Updates an existing campaign                                        |
| Delete Campaign         | DELETE     | Deletes an existing campaign                                        |
| Get Campaign            | GET        | Fetches a specific campaign by ID                                   |
| Search Campaigns        | GET        | Retrieves the latest 200 campaigns meeting the specified criteria   |
| Create Contact          | POST       | Creates a new contact                                               |
| Update Contact          | PUT        | Updates an existing contact                                         |
| Delete Contact          | DELETE     | Deletes an existing contact                                         |
| Remove Tag from Contact | POST       | Removes a tag from a contact                                        |
| Tag a Contact           | POST       | Adds a tag to a contact                                             |
| Get Contact             | GET        | Fetches a specific contact by ID                                    |
| Search Contacts         | GET        | Retrieves the latest 200 contacts meeting the specified criteria    |
| Add Note                | POST       | Adds a note to a record                                             |

&#x20;

#### Authorization <a href="#h_01j1vwmb9jrpz9a1d807zsc0mt" id="h_01j1vwmb9jrpz9a1d807zsc0mt"></a>

Your users will login to Zoho CRM via OAuth 2.0 using Integry's developer app. You can [replace it](https://support.integry.io/hc/en-us/articles/10887314172441) by [setting up your own](https://www.zoho.com/crm/developer/docs/api/v3/oauth-overview.html).&#x20;

### Limitations <a href="#h_01j1vwmb9j0c6yjtqckghq7ebb" id="h_01j1vwmb9j0c6yjtqckghq7ebb"></a>

Following are the limitations in the Zoho CRM App Connector as yet.

* The Twitter and Skype ID you use should be one word with no spaces.
* The connector does not support ‘**.cn**’ domains.


# Zoho Mail

[Zoho Mail](https://www.integry.io/apps/zm) is a secure online platform for collaborative business communications. It combines email with modern collaboration tools using comments, likes, event streaming, and sharing. The security and privacy features of Zoho Mail allow you to keep your email data safe from different types of email attacks. Zoho Mail's extensive control panel enables you to manage all the settings, customizations, and configurations - all in a single place. The Zoho Mail App Connector helps you manage and sync emails with other third-party apps.&#x20;

### Specifications  <a href="#specifications-0-0" id="specifications-0-0"></a>

Before you connect your Zoho Mail account with Integry, here are a few things you need to learn about the Zoho Mail App Connector.&#x20;

#### Authorization Type  <a href="#authorization-type-0-1" id="authorization-type-0-1"></a>

Zoho Mail uses the [OAuth](https://support.integry.io/hc/en-us/articles/11112617800985-Authentication-Types-Supported-in-Integry) authorization method, where the access token expires after an hour. A refresh token is used to generate a new access token after it expires. This won't have any impact on current integrations if implemented properly. This authorization enables third-party applications (clients) to gain delegated access to protected resources in Zoho via an API. When you set up an integration, you need to allow Integry to access your Zoho Mail account.&#x20;

#### Trigger Type <a href="#trigger-type-0-2" id="trigger-type-0-2"></a>

The triggers used in Zoho Mail are Post save triggers (manual triggers). Post save trigger is a type of [webhook-based](https://tray.io/documentation/connectors/triggers/webhook-trigger/) trigger. In this type of trigger, Integry provides a link at the end of the integration setup. That link is added to Zoho Mail's website. Payload is received on this link.&#x20;

### Limitations <a href="#limitations-0-3" id="limitations-0-3"></a>

Currently, there is only one limitation of this app. The Zoho Mail connector does not support '**.cn**' domains.


# Zoom

### Introduction <a href="#h_01ha4pybpwdh2asbc0wvhg9p8q" id="h_01ha4pybpwdh2asbc0wvhg9p8q"></a>

[Integry](https://www.integry.ai/) is an innovative platform that streamlines and automates integrations between Zoom and other apps and services. By leveraging Integry, you can effortlessly connect Zoom with your preferred tools, optimizing your video conferencing experience.No more manual data transfers or repetitive tasks, as Integry allows you to create custom flows and set up triggers to automate actions across different applications.\ <br>

### Installation <a href="#h_01ha4pybpx5qc4vftfvtqj0mts" id="h_01ha4pybpx5qc4vftfvtqj0mts"></a>

1. Sign up for an account on [integry](https://www.integry.ai/)'s website.
2. Once logged in, navigate to the "Flows" tab and create a new flow from scratch.
3. Add a trigger or setup a step, and then add Zoom as your child step.
4. Select the action you want to perform.<br>

   <figure><img src="/files/k18XLyX0HNboYptrdDv1" alt=""><figcaption></figcaption></figure>
5. Clicking "Add my account" will open a consent screen popup if you are logged in.\
   \
   \
   Once your account is connected successfully, click "Continue."

   <figure><img src="/files/c1leLrkbIArzqieuf3gF" alt=""><figcaption></figcaption></figure>

   <figure><img src="/files/L8X5SV62nGfAVUvBe5xz" alt=""><figcaption></figcaption></figure>
6. Configure your action by providing values, or press the + button to get values from a previous step of the flow.

   <figure><img src="/files/vCXnHnvVtSf7yZa2tK8f" alt="" width="375"><figcaption></figcaption></figure>
7. Once configured, you can publish the flow to a marketplace to create your integration.

### Disconnect/Remove Connected Account <a href="#h_01ha4pybpxk1wa20s7b8bfc94y" id="h_01ha4pybpxk1wa20s7b8bfc94y"></a>

You can follow these steps to remove a connected account:

1. Click on your account.
2. Select 'Edit.'
3. Press the trashcan icon next to 'Connected.'
4. Confirm the action to remove your account.<br>

   <figure><img src="/files/7dSA9WpskECeOvhDLo30" alt=""><figcaption></figcaption></figure>

### Usage  <a href="#h_01ha4pybpxmfttpsxwytdyrvzv" id="h_01ha4pybpxmfttpsxwytdyrvzv"></a>

Using the Zoom connector, you can set up the following integrations.When something happens in your app:

1. "*Add* **registrant to a webinar** in Zoom."
2. "*Update* **registrant's status** in Zoom."
3. "*Delete* **registrant from a webinar** in Zoom."

### Benefits <a href="#h_01ha4pybpx758rh4bh1wc45k7f" id="h_01ha4pybpx758rh4bh1wc45k7f"></a>

With our advanced capabilities, you can unlock the following benefits:

1. Save time and effort by automating repetitive tasks between Zoom and other tools.
2. Ensure seamless collaboration by connecting Zoom with your favorite productivity and communication apps.
3. Eliminate data silos and maintain consistent information across your software stack.
4. Improve team efficiency and productivity by automating workflows and reducing manual intervention.
5. Rest easy knowing that [Integry](http://integry.io/) adheres to stringent privacy measures, keeping your data secure and confidential.

With [Integry](http://integry.io/)'s powerful integration capabilities, you can maximize the potential of Zoom and enhance your video conferencing experience. Whether you're a team of remote workers, a sales team, or a project management group, [Integry](http://integry.io/) empowers you to work smarter and accomplish more with Zoom.


# Overview

{% embed url="<https://www.youtube.com/watch?ab_channel=Integry&v=S4eBc9crw94>" %}

## What is Integry Flows? <a href="#h_01hqnsten2zpbbqw08fwb0psje" id="h_01hqnsten2zpbbqw08fwb0psje"></a>

Integry is an Integration Platform as a Service (iPaaS) that allows you to add an integration marketplace to your product in minutes.

You build flows between your app and up to 250+ other apps. Your users get a fully native integration experience within your product. Their data moves seamlessly between their apps.

## What's included? <a href="#h_01hqnt8hx7tze5gy23e286s3gx" id="h_01hqnt8hx7tze5gy23e286s3gx"></a>

Integry Flows comes with:

* Ready-to-use authentication, triggers, queries and actions of [270+ apps](https://www.integry.ai/apps)
* An intuitive, powerful, low-code [flow builder](/flows/overview) that you will use to build one-way, or two-way, flows between your app and other apps
* A customizable marketplace UI that you will embed in your app (using an SDK) where your users will discover, setup and manage their integrations
* Detailed logs of integration runs with customizable error notifications enabling you to proactively support your users
* User-level reporting and adoption notifications to effectively drive usage and ROI
* A robust, scalable, secure backend with SOC 2, GDPR and CCPA compliance

{% hint style="info" %}
We are in the process of migrating Flows help docs. For now, please go [here](https://docs.integry.ai/hc/en-us/articles/28305439384473-Build-a-Flow).
{% endhint %}


# Flow Tutorials

Here's a collection of common scenarios&#x20;


# Sync data TO another app from your app

In this tutorial, we will:

* [Create a flow **from your app** **to another app**](#h_01hev188pb696nwg83zdnc0e1n)
* [Set up an integration of that flow (like your users would)](#h_01hev2zavgk1s46ekb4mgvr37g)
* [Run the integration by calling a URL from an HTTP client](#h_01hev4chz4zw5bwp9z0jhthvb1)

If you'd like, you can also [create a flow that syncs data FROM another app](/flows/markdown/sync-data-from-another-app-to-your-app) to get started.

It will only take 5 minutes. Let's begin.

### Build a Flow <a href="#h_01hev188pb696nwg83zdnc0e1n" id="h_01hev188pb696nwg83zdnc0e1n"></a>

1. Click [Create a Flow](https://app.integry.io/platform/flow/create)
2. Select a Trigger. In this example, we will select "Webhook" by Integry. This will let us invoke this Flow by calling the Webhook URL, more on that later.\ <br>

   <figure><img src="/files/Q8FsLfYeUktslUEWgaaM" alt=""><figcaption></figcaption></figure>
3. Select your app in the App field. Paste a sample json of the object that we will push from your app to Integry. Lastly, give this json payload a name.\ <br>

   <figure><img src="/files/2d0vIgRx0M8WOccJYgtW" alt=""><figcaption></figcaption></figure>
4. Add a step to perform an action in another app. In this example, we will select "Add Subscriber" in Mailchimp.\ <br>

   <figure><img src="/files/v5WBtQg8zQp3AVhLvG6p" alt=""><figcaption></figcaption></figure>
5. Rename the flow and click Save.

That's it! The flow is ready for you to try. For that, head back to the Flows list.

### Set up an integration of the flow <a href="#h_01hev2zavgk1s46ekb4mgvr37g" id="h_01hev2zavgk1s46ekb4mgvr37g"></a>

1. Click Embed.
2. Click Generate Code.
3. Open the downloaded HTML file in the browser.
4. You'll see the flow you created. In this example, that's "Sync new contacts to Mailchimp". Click Setup and enable.
5. Login to Mailchimp.
6. Configure Mailchimp.
   1. Select the audience in which the subscriber will be created.
   2. Map the email field.
   3. Select the default subscriber status.
   4. Map any other fields and click Next.
7. Before we click Save to complete the setup, we need to do one small thing so we can access the URL we'll have to call to run this integration. Assuming you're using Chrome... click View > Developer > Javascript Console.
8. Now, click Save to initialize the integration.

Almost there! The integration is now live and ready to be triggered.

### Run the integration <a href="#h_01hev4chz4zw5bwp9z0jhthvb1" id="h_01hev4chz4zw5bwp9z0jhthvb1"></a>

1. Right-click the URL shown in the console, and click Copy link address.<br>

   <figure><img src="/files/bauoojmt2g5DJzPUuaJR" alt=""><figcaption></figcaption></figure>
2. Open Postman.
3. Set the method to POST.
4. Paste this URL.
5. Go to Body, select 'raw', click Text and switch that to JSON.
6. In the Integry app, go to Account Settings > Objects.
7. Select the object you selected while creating the flow. In this example, we selected "Contact".
8. Copy the JSON payload.
9. Paste the payload in the body in Postman.
   * If you want, you can modify any of the values.
10. Click Send to run it.

We're done! Head over to Mailchimp to see the new subscriber you just created.

Recap: You created a new flow, set up an integration of that flow, triggered it, and it ran.

You can now see how the run executed by clicking the count of users against this flow (in the flows list) and drilling down to runs.

Next, let's [Embed the Flows widget](broken://pages/3ocPBOvWARUN7bAf1292) so your users can set up integrations from within your app.


# Sync data FROM another app to your app

A Flow moves data from one app to another. A Flow can have one or more Triggers that execute steps when run. Flows can sync data from or to your app from another app.

In this quick tutorial, we will build and run a flow that sends every new subscriber in a Mailchimp audience to your API endpoint.&#x20;

To make things interesting, you will get to map custom fields in your Mailchimp account to fields of the API endpoint.

{% hint style="info" %}
**Note:** You will need to login to a Mailchimp account, sign up for a [free trial](https://login.mailchimp.com/signup/?plan=free_monthly_plan_v0\&subscribers=500)
{% endhint %}

#### Create a flow <a href="#h_01hev188pb696nwg83zdnc0e1n" id="h_01hev188pb696nwg83zdnc0e1n"></a>

1. Navigate to Flows and click [Create a Flow](https://app.integry.io/platform/flow/create) button
2. Select the trigger: "Subscriber Created" in Mailchimp.<br>

   <figure><img src="/files/o0WKm36eCTiq6ePzONDR" alt=""><figcaption></figcaption></figure>
3. Click "Add a step" and select "HTTP Call". We will use this to call your API with the Mailchimp Subscriber data. If you don't have an API, Integr can write to your database, or Integry's own local store and expose an API.

   <figure><img src="/files/EDKZsk7vRkrtA8Ac2TOR" alt=""><figcaption></figcaption></figure>
4. Configure the HTTP Call: in this example, we will use [webhook.site](https://webhook.site/) as a sample API endpoint
   1. On webhook.site: Click "Copy" to copy the unique URL<br>

      <figure><img src="/files/5SOA43mFRS8l7sem81EG" alt=""><figcaption></figcaption></figure>
   2. Back in Integry's HTTP Call: Set the method HTTP call method to POST, and paste the URL.&#x20;

      <figure><img src="/files/FPKsbDGt9LpTHig3gCcP" alt=""><figcaption></figcaption></figure>
   3. Switch to the "Body" tab of the HTTP call
   4. Define the JSON payload. In this example, we will send three fields to the API endpoint.
      1. Paste this JSON in the body:&#x20;
         * ```json
           {
              "email":"",
              "first_name":"",
              "last_name":""
           }
           ```
      2. Map the email field from the trigger to the body.
         1. Place your cursor in between the "" you just added, and click +. The mapping menu will popup.&#x20;

            <figure><img src="/files/gQsmSOI4ScTb5QFn5alo" alt=""><figcaption></figcaption></figure>
         2. Click "Subscriber Created" under the Subscriber Created (Block)
         3. Click the ">" next to "Out" to access the output.&#x20;

            <figure><img src="/files/VvgDWpHMZ7gnHLPdMbKx" alt=""><figcaption></figcaption></figure>
         4. In this example, event type and timestamp are at the root, while the data is in an array. Click "data" to open the array, and click "email".

            <figure><img src="/files/CUT2KIMZS9YMyxSuhgUc" alt=""><figcaption></figcaption></figure>
         5. Confirm that the body looks like this: <br>

            <figure><img src="/files/oAHesy7KKyIrNgsaYAq0" alt=""><figcaption></figcaption></figure>
         6. Now would be a good time to rename the flow and save it.
      3. Add the other two fields to the setup form.
         1. Click "Add fields to setup form..." at the bottom of the body container.
         2. Unselect "email" because we already mapped it. We want the user to map the other two at setup time. You can rename the titles if you want.&#x20;

            <figure><img src="/files/3lRzPOgoJPv5HMJ4riAT" alt=""><figcaption></figcaption></figure>
         3. Click "Add fields".
         4. Click "Setup Form" in the left pane, and go to the second page. Instead of "Acme Co.", it should have your app's name. You will see the two fields that you just added.&#x20;

            <figure><img src="/files/NaGWu1EJGdu88Sd6FkII" alt=""><figcaption></figcaption></figure>
         5. Click "First Name" or "Last Name". You can see that the fields have been automatically configured to allow users to map fields from the trigger step. You don't need to do anything.
         6. Go back to "Trigger Blocks" and to the "Body" tab in "HTTP Call". You will see that the fields in the setup form (that you just added) have been automatically wired as the values of the fields to be sent to the API endpoint. You don't need to go anything here either. <br>

            <figure><img src="/files/ixQHsv4TihI1K1cGlHdk" alt=""><figcaption></figcaption></figure>
   5. Now, simply Click "Test" to run this HTTP call to confirm that it's working.&#x20;
      1\.

      ```
      <figure><img src="/files/2hBsaEOzpeHAnguFZ2JW" alt=""><figcaption></figcaption></figure>
      ```

      2\.  Integry will ask you to provide an API key. Enter "123" and click Proceed.

      ```
      <figure><img src="/files/YZrbvFpvkB1SKBEkO0JZ" alt=""><figcaption></figcaption></figure>

      * You see this screen because Integry is assuming that webhook.site is your app, and the API call to the endpoint has to be authenticated with your credentials. Don't worry, your users won't have to give the API key in this manner because you will pass the key through the SDK when you embed the widget.
      ```
   6. You can see the request and response below.&#x20;

      * "email" contains a sample value from the trigger's output that you mapped.
      * "first\_name" and "last\_name" are empty because they've not been mapped as yet. You will get to map them (like your users) in the next section when you setup an integration of this flow.

      <figure><img src="/files/EAlSqPynAWvJsDyjSlzn" alt=""><figcaption></figcaption></figure>
5. Save the flow and go back to the Flows list.

That's it! The flow is ready to use.

#### Set up an integration of the flow <a href="#h_01hev2zavgk1s46ekb4mgvr37g" id="h_01hev2zavgk1s46ekb4mgvr37g"></a>

1. Click "Embed". You'll see the flow you created. In this example, that's "Sync new subscribers from Mailchimp".
2. Click "Setup and enable".
3. Login to Mailchimp.
4. Configure Mailchimp.
   1. Select the audience you want to monitor for new subscriber and click Next.&#x20;

      <figure><img src="/files/yuMemOyTWaXBDGIiz4t4" alt=""><figcaption></figcaption></figure>
5. Configure Acme Co.
   1. Map Acme Co. fields to Mailchimp fields.&#x20;

      <figure><img src="/files/UI9ruPUYJDG3y2eA1AEy" alt=""><figcaption></figcaption></figure>
6. Click Save to initialize the integration.

Almost there! The integration is now live and ready to be triggered.

### Run the integration <a href="#h_01hexket3180hrha4jn5ybpjw5" id="h_01hexket3180hrha4jn5ybpjw5"></a>

In this example, we are using a Mailchimp trigger so steps 1-5 will happen in Mailchimp.

1. Open [mailchimp.com](https://mailchimp.com/) in a browser.
2. Log in with the same user account you used while setting up the integration.
   1. If you have multiple team accounts, select the same team account you selected earlier.
3. Click "Add subscriber".
4. Fill out the form with a new user's details.&#x20;

   <figure><img src="/files/bv1UguK5zFeYCskoyPv3" alt=""><figcaption></figcaption></figure>
5. Give permission to email the user, and click Subscribe.

   <figure><img src="/files/tcDBfYRlRZFG5XMnKfTx" alt=""><figcaption></figcaption></figure>
6. Go back to webhook.site. A new request with the details you entered should have been received.
7. You can also see how the run actually executed by clicking the count of users against this flow (in the flows list), drill down to runs, and then steps.

We're done! You just created a flow between two apps, setup an integration of the flow, and the integration ran.

#### Next steps <a href="#h_01hneavbezh46z9tyxsmgjwztw" id="h_01hneavbezh46z9tyxsmgjwztw"></a>

* Make flows that [send data to another app](/flows/markdown/sync-data-to-another-app-from-your-app), import data from an app, export data to an app, or even sync both ways between another app and your app.&#x20;
* [Embed the Integry widget](broken://pages/3ocPBOvWARUN7bAf1292) in your app so your users can set up integrations from within your app

<br>


# Create a two-way flow

### The Problem - Integration Loops <a href="#h_01hnjrheq166g66dycd8kgarav" id="h_01hnjrheq166g66dycd8kgarav"></a>

In a two-way sync integration, a change in one app is reflected in the other app and vice versa. This brings some problems with it that cannot be left overlooked while creating integration Flows.&#x20;

An update or addition of data in one app can cause continuous back and forth updates between the two synced apps, making it an infinite cycle.&#x20;

Let’s better understand this with an example.&#x20;

Consider you have created an integration that syncs your contacts between [Sendinblue](https://www.sendinblue.com/) and [MailChimp](https://mailchimp.com/). Now let’s say you update a contact’s information in Sendinblue. This will [Trigger](/getting-started/key-concepts#h_01hnbh26nyfh3rkp2jd3gwwcnp) a response from Sendinblue in the integration that will cause the contact to be updated in MailChimp as well.&#x20;

However, the reflection of this update in MailChimp will again Trigger a response. For the two-way sync to work, this update will again have to reflect in the first app. &#x20;

This is because the integration listens to all update events, and the app sends these events to their respective Triggers even if we’re the ones doing the updates. This will cause an infinite loop of back and forth updates of that contact in both apps.&#x20;

A similar problem will arise in the case of contact creation that is synced both ways.&#x20;

### The Loop Prevention Feature <a href="#h_01hnjrheq1b591wkbm5t9kkash" id="h_01hnjrheq1b591wkbm5t9kkash"></a>

To ensure you don’t get hindered by loops in your integrations, we bring you the loop prevention feature in the Flow builder. With one single click, your Flow will become free of any potential loops that can be originated. You can enable loop prevention for your Flow with the toggle button found in the Flow UI configuration section, as seen below.&#x20;

<figure><img src="/files/ANuR0hScedFmt4kCJJRh" alt="" width="375"><figcaption></figcaption></figure>

When loop prevention is turned on, its corresponding backend algorithms become available to be used in Flows. They are designed specifically to support the smooth execution of two-way sync use-cases in Flows by making sure no loops are introduced. Let’s see the mechanism behind this feature for the “Update” and “Create” use-case examples for contacts in Flows.

### Requirements for Loop Prevention Feature to Work <a href="#h_01hnjrheq155wypdbnhjpry78h" id="h_01hnjrheq155wypdbnhjpry78h"></a>

Before using loop prevention in a specific Flow, you need to set up a few things. These are the core requirements without which loop prevention is impossible.&#x20;

1. Triggers for the required operations in a use-case should be present in the Flow for both apps. The “contact updated” and “contact created” Triggers are to be used for the update and create use-cases, respectively.
2. The Actions and Triggers used in the Flow should be using Objects to handle the data.&#x20;
3. The apps being used in your Flow should have a separate “Get Record” Action implemented. This Action applies a Get call on an input Object. This is the Object on which “Update” or “Create” is being performed in the Flow. The Get call fetches the latest information on the Object (e.g., contact) and the associated data from the respective app. This “Get Record” Action is implicitly used on the backend once you enable loop prevention in the Flow. You can have this Action activity set up in your app settings and configure the Get call in the Object section.

&#x20; 4\. The **loop prevention** toggle button in the Flow should be ON.

### The “Update” Use-Case <a href="#h_01hnjrheq2knq2hdgjq012wtxe" id="h_01hnjrheq2knq2hdgjq012wtxe"></a>

The example mentioned above will have four major steps for the update use-case. There will be a Trigger for when a contact is updated in Sendinblue and an Action that will execute in response to this Trigger that will update the subscriber in MailChimp.&#x20;

Since this is a two-way sync Flow, there will be steps for this process in the reverse direction as well. A Trigger for the subscriber being updated in MailChimp and an Action to update that contact in Sendinblue.&#x20;

Please note that only the relevant Flow steps are shown in the examples for this document for simplicity and user’s understanding.

#### **1**. **Contact Updated in Sendinblue** <a href="#h_01hnjrheq2jfe2tnnpwgmxrah7" id="h_01hnjrheq2jfe2tnnpwgmxrah7"></a>

When you update a contact in Sendinblue, it will execute the Trigger at the first step of the Flow in the image shown below. As a result of this Trigger, the Action to update that subscriber in MailChimp will be performed at the next step. &#x20;

<figure><img src="/files/e3uo9zdFXccq72KaGMUi" alt="" width="375"><figcaption></figcaption></figure>

&#x20;

#### **2**. **Subscriber Updated in MailChimp** <a href="#h_01hnjrheq2zvfece2jjyvbk1br" id="h_01hnjrheq2zvfece2jjyvbk1br"></a>

Continuing the above example, it has already been mentioned that this Flow is a two-way sync between apps. So there will also exist a Trigger in this Flow for when a subscriber is updated in MailChimp and an Action to update that contact in Sendinblue. These steps are shown below.&#x20;

<figure><img src="/files/1zEiErRzCX81iyXHpA7u" alt="" width="375"><figcaption></figcaption></figure>

In our current example, the contact was updated in Sendinblue and has already been updated in MailChimp. The Trigger shown above will now be executed. However, this time, the process will not continue to the Action as the update has already been performed. Thus, the loop will be discontinued. All of this is controlled through the backend algorithm.&#x20;

### The “Create” Use-Case <a href="#h_01hnjrheq2gnzng0fr5yqfd8zm" id="h_01hnjrheq2gnzng0fr5yqfd8zm"></a>

Along with the “update contact” use-case, loops can arise from the “create contact” use-case as well. For loop prevention in this use case, we implement a similar type of algorithm as talked above. This use-case will again have four major steps in the Flow. Let’s see the details below.&#x20;

#### **1.** **Contact created in Sendinblue** <a href="#h_01hnjrheq2t88g531zk0m6yqbe" id="h_01hnjrheq2t88g531zk0m6yqbe"></a>

When you create a contact in Sendinblue, it will execute a Trigger for “contact created in Sendinblue.” Let’s again make this the first step of the Flow, as shown in the image below. As a result of this Trigger, the Action to create that subscriber in MailChimp will be performed at the next step.&#x20;

<figure><img src="/files/4lzARJnqGB41LgzrgQaR" alt=""><figcaption></figcaption></figure>

#### &#x20;**2. Subscriber created in MailChimp** <a href="#h_01hnjrheq2zz9qgrtae22xkfkn" id="h_01hnjrheq2zz9qgrtae22xkfkn"></a>

For two-way sync in contact creation, there will also exist a Trigger in the Flow for when a subscriber is created in MailChimp and an Action to create that contact in Sendinblue. Let's assume they are the steps shown below.&#x20;

<figure><img src="/files/BdwJ9RdMWsKxMtUBpp3w" alt=""><figcaption></figcaption></figure>

Once again, as the contact has already been created in both the apps, the above Trigger will not prompt the Action step to run, and the process will be discontinued after the contact is created in both apps once.&#x20;

So the loop will be prevented. Similar to the above examples, you can use the loop prevention feature in all your two-way operations in the Flow that might prompt a loop to occur.&#x20;

Just make sure you have fulfilled the requirements for it mentioned in this article. Using the loop prevention feature may affect your task usage for the integration.&#x20;


# Build a Flow

With Integry's low-code flow builder, you can create flows to sync data from/to (or both) [250+ apps](https://www.integry.ai/apps) and your app in minutes using ready-to-use triggers, queries and actions.

A flow moves your user’s data between your app and another app. Flows can sync data from another app to your app, to another app from your app, or both.

For example, lets create a flow that will trigger when a contact is created in Hubspot, look it up in Acme, update the contact in Acme (if it's found) or create a new contact in Acme.

### Create a Flow <a href="#h_01hrwa95dd8fh7mm8kjzpcjkc6" id="h_01hrwa95dd8fh7mm8kjzpcjkc6"></a>

Go to the Flows page and click **Create New Flow**. You can rename it by clicking the name at the top.

### Select a Trigger <a href="#h_01hrsqrvfjsx67c09bm5q5x420" id="h_01hrsqrvfjsx67c09bm5q5x420"></a>

A flow must have at least one trigger. The trigger can be a webhook, a scheduler, or when the integration is initialized by the user. The webhook can be from your app, or choose from 200+ events in other apps.&#x20;

A flow can have more than one trigger. This is useful if, let's say, you want the integration to sync when a Contact is Created or Updated.&#x20;

### Add a Step <a href="#h_01hrsqs8w3bpbn59n003k2w0mg" id="h_01hrsqs8w3bpbn59n003k2w0mg"></a>

You can add pre-built actions of 250+ apps (or make a custom HTTP call yourself), make an HTTP call to your app, execute custom code, add control steps, etc. For a full list of steps, go [here](https://docs.integry.io/hc/en-us/articles/30060054060953).

Click the **+ button** below (or above) a step in the flow to add a step.

### Map Fields (or get User Input) <a href="#h_01hrwaemdfhpttqbwcs7a1gbye" id="h_01hrwaemdfhpttqbwcs7a1gbye"></a>

A field in the output of one step can be used as the input of a field of a step downstream. Click the **+ button** to browse the output of upstream steps.

If you would rather have the user map the field, or input/select a value, add it to the setup form.

### Test the Flow <a href="#h_01hrwa95ddhqv1gbs7022tve3a" id="h_01hrwa95ddhqv1gbs7022tve3a"></a>

You can run and test all the steps in a trigger block by clicking **Test this trigger block**. We will send a test trigger with a sample payload to run the block. If you want, you can modify the test payload.

If the Flow has more than one trigger, you can switch to the other trigger(s) and test.

### Add the Flow to the Marketplace <a href="#h_01hs95wjrs3hcrg0ga7wypp427" id="h_01hs95wjrs3hcrg0ga7wypp427"></a>

Once you're happy with the flow, add it to the marketplace so your users can use it.


# Trigger a Flow

## Event in another app

Integry offers 200+ ready-to-use triggers for popular apps. Simply add it, configure it (if needed), and you're good to go.

Some triggers [instantly receive new data](#h_01hr564dmfajbt87rj45ja14y0) (via webhooks) while others use [polling to get new data](#h_01hr564fqgbsnm9yz0heqz2efz).

### Instant <a href="#h_01hr564dmfajbt87rj45ja14y0" id="h_01hr564dmfajbt87rj45ja14y0"></a>

Instant triggers use incoming webhooks. Whenever there is new data, the app will call the Integry webhook URL with the event data in the payload.

### Polling <a href="#h_01hr564fqgbsnm9yz0heqz2efz" id="h_01hr564fqgbsnm9yz0heqz2efz"></a>

If the app does not support webhooks for a particular event (eg. Contact Added to a List in HubSpot), a polling trigger can be used. A polling triggers works by:

1. Establishing a baseline of existing data when the integration is setup
2. Checking (or polling) for new data every 5 minutes
3. Running the trigger block in the flow for every new record found

## Webhook <a href="#h_01hrsr5f4rawex3d4bqmrtdjck" id="h_01hrsr5f4rawex3d4bqmrtdjck"></a>

When a particular event occurs in your app, you can trigger a flow by calling a webhook and passing a JSON payload. Let's say, you're building a flow, *When a contact is creating in AcmeSaaS, add a subscriber in Mailchimp list*. Your app will send a JSON payload to Integry when a contact is created in your app. That payload could look like this:

```json
{
    “id”: 123,
    “email”: “john@appleseed.com”,
    “first_name” : “John”,
    “last_name” : “Apple”
}
```

You can also name the payload if you want to pass different sample fields and/or values in the marketplace embed code.

## On schedule <a href="#h_01hrsr5h5zsjegw0y3gpag6dbk" id="h_01hrsr5h5zsjegw0y3gpag6dbk"></a>

A flow can be triggered on a schedule.

## Integration created <a href="#h_01hrsr5khn1b9bcpzvdn55765m" id="h_01hrsr5khn1b9bcpzvdn55765m"></a>

This is useful if you want to want to execute any steps when the integration is setup by your user. For example, you can register the webhook URL by making an HTTP call.




---

[Next Page](/llms-full.txt/1)