Track Flow Activity in Integration Logs

Integration logs are most useful when they clearly show where each action came from.

When an app contains multiple flows and integrations, it can be difficult to identify which flow triggered a specific log entry. Adding the flow name directly to each entry makes troubleshooting much faster.

Identify the Source Immediately

Each integration log entry now shows the name of the flow that was running when the integration was triggered.

This makes it easier to understand:

• Which flow started the action
• Where an error occurred
• Which process needs to be reviewed
• Whether the correct flow triggered the integration

Faster Troubleshooting

Without a flow name, investigating an issue may require checking several flows and comparing their activity.

Displaying the name directly in the log removes that extra work. You can immediately open the relevant flow and focus on the right place.

This is especially helpful in larger apps where multiple flows may use the same integration or perform similar actions.

Because troubleshooting is much easier when the logs tell you where to look.