Agiled Docs

Installed apps can support import, sync, or both. Use runs to bring provider data into Agiled, refresh connected records, and troubleshoot provider errors.

Run imports and syncs deliberately. Provider data can create or update many records at once.

Run an Import or Sync

Open Settings > Apps.
Open the installed provider.
Review the connected account and object scope.
Select Import or Sync if the action is available.
Wait for Agiled to start the run.
Review recent runs for status and errors.

Before Running

Confirm the provider account, workspace, date range, object types, and source of truth. If the integration can affect many records, run the smallest practical scope first.

Tell affected teams before running a large import so they do not edit the same records while data is changing.

If the provider has multiple companies, workspaces, mailboxes, calendars, or projects, open the provider in another tab and confirm the exact source before starting. Most bad imports begin with the wrong account or workspace.

Import vs Sync

Import usually brings provider records into Agiled without pushing Agiled changes back to the provider.

Sync can refresh data in both systems when the provider supports bidirectional sync.

Before running sync, confirm which system is the source of truth for each object. This prevents overwriting newer or cleaner data with stale provider values.

Review a Failed Run

Check:

The provider account is still connected.
The provider credentials or OAuth authorization have not expired.
The provider account still has access to the selected workspace, company, calendar, project, or list.
The error message names a missing permission, rate limit, invalid credential, or unavailable provider API.

Copy the exact error and run time before retrying. If provider rate limits or permissions caused the failure, retrying immediately usually repeats the same failure.

Review A Successful Run

Successful does not always mean the imported data is ready to use. Spot-check created and updated records, duplicate behavior, relationships, and owner or status fields.

Check a sample from the beginning, middle, and end of the run. Provider data can vary across older and newer records, especially after migrations or permission changes.

Open the destination module after the run. For example, check CRM contacts after a contact import, projects after a project import, and invoices or payments after a finance sync. The run log tells you what happened; the module confirms whether the data is usable.

Retry Safely

Before retrying a failed run, check whether it partially imported data. Fix the provider permission or mapping issue first, then rerun a small scope when possible.

If the first run created duplicates, stop and clean the duplicate-matching problem before retrying. A second run can make cleanup harder.

Run Review Checklist

After every important run:

confirm run status and time
review error messages or skipped records
spot-check created records
check duplicate matching
confirm owners, statuses, dates, and relationships
compare a few records with the provider
document any cleanup needed before the next run

Avoid scheduling repeated syncs until the first manual run produces trustworthy data.

Document Important Runs

For migrations or large imports, record the provider, account, date range, run time, object scope, and cleanup notes. This helps explain later why records appeared or changed.

Sync and Import Runs