Activity Tracker: Audit Trail and History

Track every operation, including timing, record counts, user details, and more.

Monitor operations with:

• Timing information: Start and finish dates and times, and duration of the operation
• Record statistics: How many succeeded, failed, were updated, created, deleted, or unmodified
• Operation type: Selected CRM, module or app, object type, and template
• User and account details
• Automation: Manual vs. automated operation
• Mode: Preview or update
• Recipe correlations: Which templates were run, and the results for each

A Run ID is a unique identifier assigned to each operation performed within Insycle. It serves as a reference point for tracking and reviewing specific changes made to your data or Preview operations.

Use it to:

• Get help from support when looking at a specific issue
• Look up the Run ID in a CRM record, then find the relevant operation information in Insycle
• Locate a Run ID in a CRM record to reference when making support inquiries
• Download the CSV reports that contain detailed change information for update mode operations
• Search for operation reports in your email inbox
• Collaborate with your team

This Run ID appears in the emailed report subject line, the attached CSV file name, and in the Result popup. 

You can also add a custom Run ID property to your CRM to gain record-level insights into data modified by Insycle. This captures the same Run ID found in the Activity Tracker so you can review the full report and statistics for the process.

Learn more about setting up the Run ID fields for each object in your CRM.

The detailed CSV reports downloaded from the Run ID links provide a before-and-after view of the affected records. These reports can be downloaded from the Activity Tracker for operations run in Update mode.

For each record processed, the CSV download includes:

• Result of the action
• Message with details
• Record ID and Email or Name
• Deeplink to the record in the native CRM (direct link to the record)
• Before-and-after view of the data from affected fields
• Additional fields determined by the module used and configuration

Open the CSV file in a spreadsheet application and review the values for each row. You can see the (Before) and (After) values side-by-side. For example, Job Title (Before) and Job Title (After).

Navigate to Operations > Activity Tracker. The list shows the most recent operation at the top.

Enable the Show Preview toggle (yellow) to include preview operations in the list.

Use the filter to search by object type, template name, or Run ID, or use the Start Date and End Date selectors to narrow the results by time period.

Click a column header to change the sort order.

Use the pagination controls below the list to navigate through the history.

The Activity Tracker table includes key statistics about every operation:

Record Counts

• Updated: Total number of records modified by the process
• Created: How many new records were created in the CRM
• Deleted: How many records were deleted from the CRM
• Failed: The number of records the operation could not run on (view the Message text in the CSV for details on why each record failed)
• Succeeded: The number of records the operation was able to run on, whether the action was update, create, delete, or something else. If this value is zero, this indicates there were no records that matched your criteria 
• Unmodified: Total number of records not modified by the process

Operation Mode

• Preview: Checked if the operation ran in Preview mode; unchecked means Update mode
• Recipe: Checked if part of a Recipe. Hover to see the corresponding Recipe Run ID, when applicable
• Manual: Checked if the operation was triggered manually; unchecked if it was automated

Insycle's Recipes let you combine multiple Insycle templates into a structured, multi-step process for automation, workflow integration, and organization.

You can view Recipe changes by downloading CSV reports from the Activity Tracker. Although there is no single report for all of the Recipe's operations, you can download individual reports for each operation. All operations that are part of a Recipe will be checkmarked in the Recipe column of the table.

1. The operations are listed in reverse chronological order. The Recipe row appears below the templates.
2. The Recipe's Run ID will help you determine which operations are related. 
3. You can see which templates are part of a Recipe by hovering over the Recipe checkmark. This will display the Recipe's Run ID.
4. To download the template reports, click the respective operation Run IDs.

If you click the Recipe name in the 'Template' column, you will be redirected to the Recipe page. If you click on a Template name, you will be redirected to the relevant module and template.

To learn more, see Recipes.

If an error is detected after an update, the Activity Tracker report allows you to at least partially revert an update using the data contained in the report. While this will not contain every single field for each record, it does give you an option for at least partial rollback. This feature is invaluable for quickly correcting mistakes without extensive manual effort.

To revert or undo changes made in an operation, download the corresponding CSV file for that Run ID from the Activity Tracker.

In a spreadsheet editor, make the following changes to the CSV:

• Remove columns for fields you don't need to restore
• Discard the "After" columns for the data you do want to restore

Using the Magical Import module, upload the edited CSV and map the Record ID and "Before" columns. Then import the relevant records to the CRM. Use the Record ID as the Matching Field.

The Activity Tracker is a key tool for diagnosing why operations didn't work as expected.

Review Operation Statistics

Start by examining the key metrics in the Activity Tracker table:

1. High "Failed" count: Most likely points to configuration issues, but could also indicate inconsistent data quality, or permission problems
2. Zero "Succeeded" records: This can indicate your filters were too restrictive, or no records matched your criteria
3. Many "Unmodified" records: May suggest your update rules aren't targeting the right data variations

Analyze the CSV Report

For operations run in Update mode, click the Run ID to download the report and review the information. What data populated the fields in the CSV?

Result column showing "Failed." Check the Message column for specific error details like "Change rules in Step 4 'Master Selection'" or "Unmodified, no matching record found."

Empty "After" values. May indicate mapping issues or that the source data was blank.

Unexpected data transformations. Compare the (Before) and (After) columns to spot logic errors in your template configuration.

Next Steps

• Click the template name to review and adjust your configuration
• Use Preview mode to test changes and see if you get better results
• Consider breaking large operations into smaller, more targeted batches

There are two main ways to monitor the progress of long-running operations.

Operation Completion: Periodically Check the Activity Tracker

All operations will appear in the Activity Tracker once they have been completed. To see Preview operations, enable the Show Preview toggle (yellow = on).

Operation Progress: Periodically Refresh the Template

While the operation is still in progress, you can use the template to view the progress. Under Step 1, click the Find or Search button.

Look at the number of results in the Record Viewer.

Wait a few minutes and refresh the page. You should see the number of results reduce as Insycle processes the operation.

When using automations, timing is important. If processes are not executed in the correct order, the necessary property value might be set in the CRM after the workflow reaches the Insycle step, or vice versa.

In your CRM, check the timestamps on modified records.

Then go to the Insycle Activity Tracker and locate the process that ran during the operation. In the Started column, is the timestamp before or after the time the CRM change was made?

If the Succeeded value is "0," it may indicate that your workflow relies on a specific CRM value to trigger the change, and this value didn't exist prior to the Insycle automation step.

To give you record-level insights into data changed by Insycle in your CRM, you can add a custom property, Insycle Run ID. This captures the same Run ID found in the Activity Tracker for each Insycle operation that updates or creates a record.

For each object type you use with Insycle, add a new custom property with the label "Insycle Run ID". This field label is the only requirement for the integration to work properly. It's not dependent on the internal name or underlying API field name.

Once set up, each time you run an operation in Insycle on your CRM data, Insycle will automatically populate the field, allowing you to refer back to the Run ID in the record history. 

When using an Insycle Recipe that includes templates for multiple object types, such as companies and contacts, the same Run ID will appear in both records.