Overview

Connector setup is really about permissions, scope, and review boundaries rather than just checking a box on an integration list.

The business has to decide which systems the employee may touch and what the employee is allowed to do in each one.

Without that clarity, even a useful workflow can become risky or confusing the first time it touches a real record.

Good connector setup keeps the agent helpful while making sure the owner still controls the tools that matter most.

Practical examples by business type

• A home service business may connect email and calendar so new requests become readable summaries and schedule-ready options.
• A sales team may connect the CRM so lead notes, qualification details, and follow-up tasks are organized in one place.
• A phone-heavy office may connect call notes or voicemail handling so the front desk does not have to rewrite the same information by hand.
• A form-driven business may connect web intake to the inbox or task system so requests are easier to route.
• A consulting firm may connect only the systems needed for summaries and follow-up, while leaving sensitive records out of scope.

Detailed checklist or step-by-step section

Connector setup should always start with the question: what is the minimum access needed to make the workflow useful? That question keeps the scope small and makes review easier.

A second important question is what happens if the connector is revoked. The team should know how to disconnect access, who can do it, and how to confirm that no further action will be taken.

How to apply this with your own agent

1. Inventory the systems the workflow truly needs.
2. Decide whether each system needs read-only or write access.
3. Define which fields the agent may see and which it should never touch.
4. Test the workflow in a narrow lane before broadening access.
5. Keep a revocation and audit trail so the owner can remove access quickly if needed.

What to consider before building this agent

• Connector setup is a permissions problem as much as a technical one.
• If a connector is not needed for the first version, it should stay out of scope.
• The owner should know who approved each connection and why it was added.
• Approved access should be narrow enough that the workflow can be explained in plain English.

Where a Custom Built Employee helps more than a generic AI tool

• A Custom Built Employee can be configured with the exact connector list the business approves.
• A generic AI tool may talk broadly about integrations, but it often does not show the access model clearly.
• A managed setup can keep one system read-only while another receives drafted notes or routed tasks.
• Custom configuration matters when the business wants access to be intentional rather than broad and invisible.

Common mistakes to avoid

• Giving broad write access when drafts or read-only access would do.
• Connecting systems just because they are available.
• Forgetting to define the revocation process.
• Leaving the audit trail vague.
• Assuming connector access is harmless simply because the workflow is small.

Questions to ask before setup

• Which systems are truly required?
• What level of access is needed in each system?
• What should stay human-reviewed even if the connector exists?
• How will the owner revoke access if the workflow changes?
• What should the audit trail show after a test run?

Ready to build this safely?

• Custom Built Employee - Define the smallest useful connector scope before anything is enabled.
• Services - Review the setup and workflow design that usually comes with connector planning.
• Contact - Talk through access levels, revocation, and audit trail requirements.

A practical way to keep connector scope under control

Connector setup is easiest to review when the business starts with the smallest useful scope. If the employee only needs to draft, do not give it send rights. If it only needs summaries or notes, do not give it record mutation rights. If it only needs to suggest time windows, keep the calendar lane narrow and review-gated until the owner is comfortable with the behavior.

A clean connector plan also makes the audit trail easy to read. The owner should know when access was added, who approved it, what the agent may read, what it may draft, and how to revoke that access if the workflow changes. That is the difference between a useful setup and a permission bundle that nobody can explain later.

In practice, the best connector plan is the one that makes the workflow easier without widening the authority boundary more than necessary. A Custom Built Employee can help when the business wants email, CRM, calendar, or phone access to stay intentional rather than broad and invisible.

A strong connector plan also gives the owner a plain answer for each scope question. What can the employee read, what can it draft, and what can it actually change? If the answer is not obvious, the workflow is still too broad. Keeping that answer small and clear is what makes the setup reviewable later, especially if the business adds another system in the future.

A good setup also keeps the owner from confusing availability with authority. Just because a system can be reached does not mean the agent should be able to use it broadly. That distinction is what makes a managed setup feel safe enough to trust.

Important setup notes

• Do not imply connector access is live by default.
• Always describe email, CRM, calendar, and phone access as setup-dependent and approval-bound.
• Avoid language that suggests the agent can mutate customer data without oversight.
• Keep the article focused on permissions and workflow shape instead of broad automation claims.

Suggested Internal Links

• AI Employees
• How to prepare
• Custom Built Employee
• Contact