The Integration View is designed to give detailed information on the status of the integrations created against a Flow by your end-users. It also provides visibility of all events taking place inside the integration. Using this, you get the means to debug integrations, check the tasks being consumed by an end-user or an integration, or see if every step of the Flow is performing as intended.
To open the integration view, go to the Flows tab in your dashboard and hover over the stats of any Flow. You will be able to see the "View Integrations" tooltip as shown in the above image.
If no integrations have been created against a Flow, you will see a "No integrations to see" tooltip on hover, and the stats will not be clickable.
Once you click the Flow stats, you will be taken to the end-user information for that Flow, as shown below.
This will show you all your end-users who have made an integration using this Flow. This is ordered by the most recent end-users first.
On the top left, you will be able to see the Flow name, ID, and the stats. In the middle, you'll see the end-users and their registered details. If your SDK is set up to receive the username and profile image, then these will appear here. Here is how you can set these up. If these details are not provided, you'll just see the user IDs.
You can also copy a user ID by hovering over it and clicking it.
For each user, you'll see their number of total integrations, the number of total tasks consumed, and the status of the user. A user can have different statuses based on their integrations.
Here are all possible statuses that a user can have:
a) Active: The user has at least one active integration.
b) Inactive: The user has no active integrations.
c) Paused: The user has reached their task limit.
d) Auth Missing - The user's authentication for an integration is not found or has been deleted.
e) Creation Failed - An integration creation process for this user has failed, and the setup was unsuccessful.
The above statuses related to integrations can be seen in more detail here.
In addition, you can click on any user from the list to see all the integrations they have created.
This will again be ordered by the recency of integrations. For each integration here, you'll be able to see its name and ID, the tasks consumed by it, the status of the integration (active, inactive, paused), and the number of runs completed by it. One complete operation in a Flow is defined as one run. More details on it can be found here.
As seen above, you can enable/disable and delete an integration by clicking on the three dots at the end of any integration. You will see the below screen when you click on Delete.
- Green is for 2xx Success which means that the request was successfully received, understood, and accepted.
- Yellow is for Loop Prevented which means we received an event from a service which would’ve caused an infinite loop
- Blue is for 3xx Redirection which is for when the server asks to go to another URL.
- Purple is for 4xx Client Errors which means that the request contains bad syntax or cannot be fulfilled.
- Pink is for 5xx Server Errors which means that the server has failed to fulfill a request.
In the User view, your health bar shows the aggregate status of all runs under that user. A run means to execute a program or to operate.
In the Integration view, it will show an aggregate for all the runs inside that integration. Inside a Flow, it will show aggregate status for all the runs inside that Flow.
In the run view, it will show the aggregate status of all the steps performed under a particular run.
Integration detail page
You can click on any integration for a selected user to see that integration's details. In the example provided above, let's say that you clicked on the "MailChimp to Hubspot" integration. This will now take you to the integration details page, which will look like this:
This page will have all the recent runs that have taken place in the integration. The name of the run is the name of the first step for that run in the Flow. Mostly, it is a Trigger step that starts a run or an operation. A run can also be started with a Setup step, as in the case of using Queries to import records.
For every run, you'll be able to see these details:
- The time when the run occurred. You'll be shown how long ago the run occurred. Hovering over this info will show you the exact time of occurrence, as shown below.
- The number of tasks consumed by the run.
- The duration taken for the run to complete.
- The link to this run in the integration logs. This will only be shown to the staff account members that have the authority to debug integrations. More information on staff accounts is provided at the end of this section.
- The status or the HTTP response of the run. This would show a green 200 status if everything in the run was successful. Otherwise, it will show a red error code for the first failed task in the run. Hovering over this status will also show the error code description. In our running example, the first run has a failed task, due to which it shows us a service unavailable error code as shown below.
Staff accounts: We have a permission system in place where we mark user accounts as "staff." If you are staff, you'll be able to see some additional details that are helpful in debugging integration issues, such as the links to integration logs.
Clicking the ellipsis at the end of a run will give you the option to copy the GUID of the step or view app detail which will show you all the apps and their ID that are part of that run.
You can also click the View More button at the bottom to see the details of older runs that have occurred.
You can also click on any run on the integration detail page to see the details of all the tasks inside that run. The run will expand, and you'll be able to see all the Flow steps inside it with the exact hierarchy. An example is shown below.
Here you can see all the tasks inside a run, including all the steps like IF conditions, Loop steps, all Actions, etc. There will be an iteration counter next to each step showing the number of iterations in that particular step. To see the steps inside the second loop iteration, you'll need to click on the View More button. Five steps will be shown on default, but clicking load more iterations will load the next five and so on. Similar to the run details, you'll be able to see the analytics for each task inside the run. These will be: occurrence time, tasks consumed, the duration for the step to complete, link to the logs, and the HTTP response code.
The tasks that have failed in this run will be colored red. It can be seen that in the current example, the conditional step at the end of the loop has failed to execute due to a 503 (service unavailable) error status. This is the reason that the overall run is showing the same error status.
As shown above, you are provided three different dropdowns to filter your run data.
With the first filter, you can show or hide internal steps in your run data. Internal steps are tasks that are performed on the back-end by Integry and are not added as steps in the Flow builder.
By default, the internal steps are hidden from your run details. But you can use the above filter to view the internal steps. In our current example, viewing internal steps will look like this:
The implicit steps can now be seen inside the loop, like using the "Get" action from the Mailchimp app, as well as the steps to fetch data from the data store.
You can use the second filter allows you to select between Show all, Failed only, Successful only, Setup steps only, Polls only, Scheduled steps only, Autohooks only, and Triggers.
With the third filter, you can choose to see the runs for a specific time frame. The dropdown options include Last hour, Last 6 hours, Last 24 hours, Last 7 days (default), No time limit, Custom, Jump to time, and From the start.
Selecting the Custom range will load two dropdowns on the left where you can select your custom dates, as shown below.
You can click on any task inside a run to see its details. This will show you all the input and output data for that task. For our current example, clicking on the Hubspot Create Contact Action will open the details as shown below.
You can select from all the possible data types found in an Activity and its endpoint. This includes all inputs and transformations (request bodies), raw responses (response body), formatted responses (object output), and headers. In our current example, we can see the Parsed Request Body Flow in Twig format set for this Create Contact Action's endpoint in the Hubspot app.
You can see the inputs and outputs of other steps in a similar manner, as shown above.
Learn how to see the insights and reports for your integrations.