Integrations

Connection checklist

A practical checklist for safely adding, verifying, granting, testing, and reviewing a business app connection in Yodu.

Use this checklist for every new app or account.

Before connecting

  • The first employee and task are already defined
  • You know which account should be authorized
  • You know whether the employee needs read, draft, or external-action access
  • A human owner can review the first test
  • The test will not affect real customers or production data

Connect the account

  1. Open Tool access → App catalog.
  2. Search for the provider.
  3. Review the app details and available actions.
  4. Select the add button.
  5. Complete the provider authorization flow.
  6. Open Connected and confirm the account appears.
  7. Give multiple accounts clear labels.

Yodu app catalog showing popular business tools and connected state

Scope access

  1. Open Employee access.
  2. Find the new account — it starts enabled for every employee.
  3. Confirm the intended employee has it enabled and pointed at the correct account.
  4. Disable the switch for employees whose roles do not need this tool.
  5. Leave the risk decision to the approval gate; the switch only controls visibility.

First tests by category

CategorySafe first testAvoid on the first test
EmailRead one thread and draft a replySending to a customer
CalendarRead upcoming eventsModifying a real executive calendar
CRMRead one contact and prepare a noteChanging lifecycle stages in bulk
BillingRead a test customer or subscriptionRefunds, charges, or cancellation
EngineeringSummarize one issue or PRMerging or deploying
SupportRead a test ticket and draft a responseClosing or replying to a real escalation
AnalyticsRead a known reportChanging tracking or retention settings

Verify the result

  • The correct employee used the correct account
  • The task and source material are clear
  • The output is visible in the channel or task
  • Any external action stopped at the approval gate before running
  • Employees with the switch disabled cannot see the tool
  • The connection remains active after the test

Troubleshooting

The account is still authorizing

Return to the provider flow and finish authorization. If it was interrupted, use the reconnect control.

The employee cannot see the tool

Confirm the account is connected and that the tool switch is enabled for that employee. A disabled switch hides the tool entirely.

The wrong account is used

Disable the switch, label the connected accounts clearly, and enable the intended account.

The requested action is blocked

Check the Approvals queue — external actions pause there by design. Deny the request when the action should not run; allow it once or for a session only when the risk is understood.

Ongoing review

Review connected accounts and tool switches monthly, and immediately after role or team changes. Remove unused accounts, disable switches employees no longer need, and rotate provider access from its settings screen when needed.

On this page