Install And Configure Apps
Connect apps from the integration catalog.
The Apps settings page lists installed and available integrations by category.
Install apps only when there is a clear workflow to connect. Unused integrations create extra credentials, permissions, and sync history for the team to manage.
Before installing, decide who owns the provider account and what records Agiled should read, write, import, or sync. This prevents connecting a personal account for a workflow the whole business depends on.
Install An App
- Open Settings.
- Go to Apps.
- Open an available app.
- Review the provider, install mode, sync mode, and object scope.
- Select the install or connect action.
Some apps use OAuth and send you to the provider. Others require credentials in the configuration form.
If the provider opens in the browser, confirm the browser is signed into the right provider account before approving access.
Before Installing
Confirm:
- provider account owner
- object types Agiled should access
- sync or import direction
- permission scope requested by the provider
- test record or test transaction to verify setup
- rollback plan if the connection imports wrong data
Open the provider's official setup or permission documentation before approving access. Provider screens and permission names can change, so use Agiled for the workflow steps and the provider documentation for the current account-side requirements.
Configure Credentials
If the app shows configuration fields, enter the required values and save. Store provider credentials securely and rotate them if access changes.
Check whether the app is for sync, import, payments, calendar, mailbox, or automation. The setup fields and expected test are different for each category.
Name or document the provider account used for the connection. Shared finance, calendar, mailbox, and CRM integrations should use an account that the business can continue to manage if a teammate leaves.
Test the Installed App
Run the smallest useful test for the app type:
- For imports, import one small object set and inspect the created records.
- For sync, update one low-risk record and confirm the sync direction.
- For payments, complete a private test payment or provider test-mode payment.
- For calendar apps, book one internal appointment and confirm conflict checks.
- For mailboxes, send and receive one test email and verify CRM activity.
Do not connect a large production workflow until the first test proves the app has the expected permissions and object scope.
After the test, record the connected provider account, owner, and recovery path in your internal setup notes.
After Installation
Review the installed app detail page and confirm the status, connected account, sync mode, and last activity. If the app creates records in Agiled, open the created record and verify ownership, dates, currency, customer, and source fields before letting the integration run broadly.
For integrations used by finance, scheduling, mail, or customer communication, assign an internal owner. That owner should know how to reconnect the app, rotate credentials, and pause the workflow if the provider has an outage.
If OAuth Fails
Return to Settings > Apps and read the connection message. Try again from the app detail panel after confirming the provider account and permissions.
If a provider asks for admin approval, use an account with the right provider role or ask the provider admin to approve the integration. After connecting, run a small sync, import, booking, payment, or send test based on the app type.
If the wrong provider account was connected, disconnect it before running syncs or imports. Then reconnect with the correct account and run a small test.