Agiled Docs

Installed apps can support import, sync, or both depending on the provider.

Import and sync are separate actions. Import usually brings a batch of provider records into Agiled. Sync keeps supported records updated after the connection is configured. Not every app supports both.

Run A Sync Or Import

Open Settings.
Go to Apps.
Open the installed app.
Review connected account, last sync time, last error, and object scope.
Select Sync or Import if the action is available.
Wait for the run to start.
Review Recent runs for status and timing.

Review Recent Runs

Use recent runs to confirm the action started and to see whether it completed, failed, or needs attention.

Recent runs show the run type, status, and created time. If a run fails, open the app sheet and check the last error, connection status, object scope, and configuration fields before retrying.

If a run completes but data looks wrong, compare one provider record with the created or updated Agiled record. Success means the run finished; it does not guarantee every mapping or relationship matched your expectations.

Open the provider record beside the Agiled record when validating a first run. Check names, dates, statuses, owners, amounts, external IDs, and relationships before running the next object type.

Before Importing

Confirm you selected the right provider account.
Confirm object scope matches the records you expect to import.
Check whether duplicates may already exist in Agiled.
Start with one provider or module at a time when possible.
Avoid repeated imports until you understand whether the provider updates, skips, or duplicates existing records.

Keep a backup or export from the provider before large imports. If cleanup is needed, you need the original source to compare counts, owners, statuses, and relationships.

Import Review Checklist

After an import, review:

number of created records
number of skipped or failed records
duplicate contacts, accounts, tasks, or products
owner and status mapping
missing required fields
one sample record against the provider source

Do this before importing the next object type.

Before Syncing

Confirm the app is connected or configured.
Confirm the runtime status is ready.
Check the last synced time.
Review the last error if one exists.
Confirm related workflows or notifications are ready for synced data.

If synced data triggers workflows, pause or narrow those workflows during the first import or sync test. This prevents imported provider data from generating unexpected customer messages or tasks.

If a Run Fails

Copy the visible last error into your internal notes.
Reconnect OAuth apps when the status says the connection needs attention.
Re-enter manual credentials when configuration has changed.
Check provider-side permissions.
Retry only after the connection issue is fixed.

Do not retry a failed run repeatedly without checking side effects. Some runs may create partial records before failing, so inspect recent records and run details first.

If a partial import created bad records, pause further syncs and clean the sample set before starting a larger retry.

Run Review Checklist

Before repeating a run:

review created, skipped, failed, and updated counts
compare sample records with the provider
check duplicate behavior
check related workflow effects
record any cleanup before the next import or sync

Sync And Import Apps