Marketplace Apps - Managing External Connections

Task-specific steps

Marketplace applications that require an outside account establish a separate connection for each business account. Installation and authorization are related but distinct steps.

1. 1Open App Marketplace inside the intended business account and review the application's publisher, permissions, data scope, pricing, and support terms.
2. 2Install the application. If it requires an external connection, complete the authorization prompt with the organization-owned account intended for this business.
3. 3Review the external provider's consent screen and grant only the scopes needed for the documented workflow.
4. 4Return to the marketplace's installed-app or connection management view and confirm the connection shows the correct account and an active status.
5. 5Configure the app's workflow triggers or actions with one test record and verify the external system receives or returns the expected data.
6. 6For a bulk installation across several business accounts, open each account and establish its connection individually; bulk installation does not automatically authorize every account.

Feature-specific checks

• Record the credential owner and renewal responsibility so the integration does not silently fail when staff changes.
• Disconnecting or reauthorizing can affect live workflows; inspect dependencies first.
• Never place an external password, secret, or access token in a workflow note or ordinary custom field.

Before you begin

“Marketplace Apps - Managing External Connections” is part of the Automation → Workflows area in Adaptive AI. Create and manage active, inactive, and draft workflows. Automation changes can affect many records at once, so the safest approach is to define the intended entry condition, action, and stopping point before publishing anything. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Write down the exact trigger, filters, expected action, and condition that should stop or bypass the automation.
• Use an internal test contact with complete sample data, a valid communication channel, and consent appropriate to the test.
• Confirm that every connected account, custom field, pipeline, calendar, or template referenced by the automation still exists and is available.
• Record the current published status and settings so you can compare behavior or restore the earlier configuration if necessary.
• Choose a quiet test window when a controlled enrollment cannot interfere with active customer communication.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Save the configuration, review every branch from top to bottom, and publish only after required fields and warnings are resolved.
2. 2Run one controlled test using known inputs and note the exact time the test record entered the automation.
3. 3Open execution history and confirm that the record followed the expected branch in the correct order.
4. 4Verify the intended message, task, field update, or status change occurred once and contains the correct merged information.
5. 5Run a negative test that should not qualify; it should remain outside the automation without producing side effects.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Confirm the automation is published and that the trigger filters match the test record exactly, including capitalization and date conditions.
• Review re-entry settings to determine whether the same record is allowed to enter again or is being correctly excluded.
• Check the first failed or skipped step in execution history instead of changing several steps at the same time.
• Verify wait steps, account time zone, business-hour windows, and scheduled-send rules when an action appears delayed.
• Reconnect or reauthorize any external service that reports an expired credential, missing scope, or unavailable resource.

Best practices

• Use names that state the audience, trigger, and outcome so another administrator can understand the automation without opening it.
• Keep entry filters narrow and add explicit stop conditions to prevent duplicate messages, tasks, or opportunity changes.
• Respect contact consent, do-not-disturb status, quiet hours, and channel-specific opt-out requirements in every communication path.
• Change one behavior at a time, test it, and document the result before expanding the automation to more records.
• Review execution errors and unexpected enrollments after launch, then again after any connected integration or template changes.