Manual Credential Apps
Connect integrations that require API keys, secrets, webhooks, or server settings.
Some integrations do not use OAuth. They ask you to enter provider credentials or configuration values into Agiled.
Manual credentials should belong to a business-controlled account whenever possible. Avoid credentials that only one teammate can recover.
Manual Credentials You May See
- API key
- API secret
- Access token
- Webhook URL
- IMAP host and port
- SMTP host and port
- Username and password
- Apple ID and app-specific password
Connect a Manual Credential App
- Open Settings > Apps or the feature-specific settings page.
- Open the provider.
- Copy the required values from the provider account.
- Paste the values into Agiled.
- Save the configuration.
- Run an import or sync if the provider supports it.
After saving, run the smallest useful test for that provider. For mailboxes, send and receive a test message. For calendars, book one internal appointment. For webhooks, send one test event. For imports, bring in a small sample before importing a full account.
Record what the credential is used for before leaving the settings page. Future admins should not need to guess whether a key powers email, calendar sync, imports, webhooks, or payments.
If the provider shows scopes or permission limits, capture those in your internal notes. Later failures are easier to debug when admins know what the credential is allowed to access.
Credential Safety
Use a credential created specifically for Agiled when the provider supports it. Rotate the credential if a teammate leaves, the provider account changes, or you suspect the credential was exposed.
Store credentials in the provider or password manager your business controls. Avoid using a personal credential that only one teammate can recover. Label the credential in the provider account so future admins know it is used by Agiled.
If a credential stops working, check provider-side expiry, revoked access, IP/security restrictions, app-password requirements, and whether the account still has permission to access the object Agiled is trying to sync.
Do not paste credentials into chat, tickets, wiki pages, or support notes. Share provider names, error messages, and last test times instead.
Credential Ownership
Record the credential owner, provider account, purpose, and rotation date in your internal password manager or operations notes. Future admins should know how to recover or rotate the credential without searching chat history.
Rotation Checklist
When rotating credentials:
- Create the new credential in the provider.
- Update Agiled.
- Run the smallest useful test.
- Confirm recent runs or delivery logs are successful.
- Revoke the old credential in the provider.
- Update the password manager or internal owner notes.
Do not revoke the old credential before the new one has been tested unless the old credential is compromised.
If the old credential is compromised, revoke it first, then reconnect Agiled and review recent provider activity for suspicious use.
After rotation, check the next scheduled sync, webhook delivery, email send, or calendar booking that depends on the credential.
Troubleshooting Manual Credentials
If saving succeeds but the integration fails, test the credential in the provider where possible, then run the smallest Agiled action that uses it. This separates invalid credentials from mapping, sync, or provider-data issues.