1.6 Setting up End User logs
Give your end users more details about the integrations they have enabled.
Last updated
Was this helpful?
Give your end users more details about the integrations they have enabled.
Last updated
Was this helpful?
To show the logs for an end user, the underlying Flows need to provide the necessary data in JSON format as the last step of the Flow in the following format (filled with example values, see the ):
The overview view (1.) will be automatically generated without having to adjust the underlying Flows.
However, the # of successful and unsuccessful records will only be shown when setting up Flows as described.
Each upsert (or create/create) step in a Flow should use manual error handling and the error path should set a dictionary such as:
In case of success, a similar step (but with a different status
) should be set, so that the results can later be easily summarized.
This part of the Flow would then for example look like this:
The same setup should be similar for other entities that are upserted.
errors
listdetails
listoverview
listFinally, all the lists are combined in the final step of the Flow:
The end of the Flow would look similar to this:
The logic and format in the Flow can be freely defined (i.e. the examples shown above are just one possibility and might not apply to all Flows).
The only part that needs to be in the same structure as shown in the documentation is the final step of the Flow.
The run status is set automatically, based on the following logic:
Success
Error
If there's at least 1 error
record and 0 success
records specified in overview
OR: If the Flow Run has status error
Finished
In cases where neither the Success
nor Error
conditions are fulfilled
Scheduled
The values for an end user will be displayed as specified (see ).
For common errors, it might make sense to validate records with a
After all steps of the Flow are finished, the results need to be summarized and transformed into the expected format. For that, it's easiest to use a , with the following SQL:
Similar to the , the Query Spreadsheet Action can be used:
Similar to the , the Query Spreadsheet Action can be used. This time, the should be the reference of the Action:
If there's at least 1 success
record and 0 error
records specified in overview
OR: If the Flow Run has status success
and the Flow is not
Future Flow Run (only if Flow has a )