Your agent+Twenty
Customer context
Read selected company records and prepare updates for review.
What access would it need?
Scope: Selected CRM records.
Permissions: Read; write only when authorized.
Connections
Give your agentthe right context.
A connection defines which information an agent can use and which actions it may take. Start with the task, then check the interface, authorization, and scope.
A connection.
A purpose.
Examples of what a supported connection could make possible.
Your agent+Chatwoot
Better conversations
Use conversation context to prepare a response for your team.
What access would it need?
Scope: Selected inboxes and conversations.
Permissions: Read; draft or send permissions separately.
Your agent+BookStack
Shared knowledge
Find relevant company instructions and include source links.
What access would it need?
Scope: Selected books and pages.
Permissions: Read-only starting point.
Your agent+Plane
Work in perspective
Use project context to prepare updates and suggest next steps.
What access would it need?
Scope: Selected projects.
Permissions: Read; changes require write access.
Proposed connection examples. These pairs are not live Peren integrations; support requires a compatible template, interface, and authorization.
A clear understanding
What has to
match?
The application must expose the information or action through an interface the chosen agent can use. A product appearing in the catalog does not establish that compatibility.
The account must be authorized for the intended scope: a project, inbox, or set of records. Reading, updating, and sending are different decisions, even when they concern the same record.
See the setup journeyChoose the interface.
A working app is the starting point. The compatible interface and connection settings still need to be established.
Check the account and scope.
Missing, expired, or insufficient authorization can prevent access while the application itself is still running.
Try a bounded request.
Confirm that the intended information is available. Inspect the result before allowing a broader task or a change to the application.