Integrations & automation

# Monitor an integration

Follow what an integration does in its Logs, Objects, Tasks and Requests tabs, trace a single run and get notified when it fails.

Updated 4 October 2026

**Who can do this:** Role level 800 or higher and the integration permission.

Every integration keeps a record of what it did. When data does not arrive, or arrives wrong, these records tell you which record was handled, what was sent and received, and where it went wrong.

## Open the activity of an integration

1. Open the side menu (☰, top right) and choose **Integrations**.
2. Click the integration. Its detail panel opens on the **Logs** tab.
3. Click a tab to switch between the views described below.

| Tab          | What it shows                                                                                                                                                                                                                                                                                          |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Logs**     | Messages the integration wrote while running, with a level: **Error**, **Warning**, **Success** or **Info**.                                                                                                                                                                                           |
| **Objects**  | Each record the integration picked up, for example one order or one position. It shows the status (**Error**, **Retry**, **Queued**, **Processing** or **Success**), the error message, the trigger, the **Instance ID** and how often it was **Tried again**. Use the copy icon to copy the raw data. |
| **Tasks**    | The units of work the integration ran, with their status.                                                                                                                                                                                                                                              |
| **Requests** | Every call to or from the other system, with the address, **Port**, **Request body** and **Response body**, or **No response**.                                                                                                                                                                        |
| **Tests**    | Saved test cases. See [Test an integration](/en/help/integration-tests).                                                                                                                                                                                                                               |

## Filter the activity

* Type in **Search logs, tasks, objects and requests** to search all four views.
* Choose a **Status** to show, for example only errors.
* Choose a **Period** to limit the dates.
* Click **Clear all** to remove the filters.

The filters stay when you switch tabs, so you can look at the same period in each view.

## Follow one record across the views

Below each row you see links such as **Tasks (3)**, **Logs (12)** and **Requests (2)**. Click one to jump to that tab, showing only the rows that belong to this record. A chip above the list (for example **Object** or **Instance**) shows why the list is filtered. Remove the chip to see everything again.

Click **Trace** on a row to open the full story of one run: the object it came from, the tasks that ran, and every log line (**LOG**) and request (**REQ**) in order. When a run is too large to show in full, use the tabs to page through the rest.

## Get notified when an integration fails

Administrators set this up for the whole platform.

1. Open the side menu (☰, top right) and choose **Settings**.
2. Click the **Environment** tab and open the **Integrations** section.
3. Under **Integration failures**, switch on **Send a notification when an integration is failing** and, if you want, **Send an email when an integration is failing**.
4. Enter the **Email recipients (comma separated)** and check the **Minimum role level that counts as an administrator** (1000 by default), which decides who counts as an administrator for these messages.
5. Optionally, switch on **Also email on functional (data) errors**, for example when a record cannot be processed.
6. Set **Minutes without a run before an integration counts as stalled (0 disables)** to be warned when an integration stops running at all.
7. Click **Save** at the bottom of the page.

The same section has two general switches: **Do not send a change back to the integration that caused it** prevents loops between two systems, and **Only trigger outbound handlers when the fields they declare actually changed** reduces unnecessary outgoing calls.

## Related articles

* [Connect other systems with integrations](/en/help/integrations)
* [Test an integration](/en/help/integration-tests)
* [View and manage notifications](/en/help/notifications)
* [Configure your environment](/en/help/platform-settings)

## Still need help?

Our support team is happy to answer any question about Transportial.

[Contact support](/en/contact)[Report an issue](/en/report-issue)

---
Canonical page: https://transportial.com/en/help/integration-logs