Add a new marketing tool to Probo
Leta adds the tool your team just picked to Probo's vendor list, then starts Probo's automated check of its website.
Letaido's Probo integration gives an AI agent your records in Probo, the open source compliance platform, so new tools and privacy requests get logged.
Compliance chores marketing teams own, checked step by step.
Leta adds the tool your team just picked to Probo's vendor list, then starts Probo's automated check of its website.
Each morning, Leta reads new emails to your privacy address and logs each data request in Probo with its deadline.
Every Monday, Leta posts the open data requests in Probo that are due within seven days or already overdue.
Leta adds a processing activity for your new campaign to Probo, linked to the tools that handle the data.
Probo is open source. Here is where each integration option fits.
| Option | Set up by asking | Explains what it found | Runs on its own | No code | Connects other apps |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | Yes | |
| Probo MCP server | Yes | Yes | Partly | Yes | Partly |
| n8n community node | No | No | Yes | Partly | Yes |
| Probo webhooks | No | No | Yes | No | Partly |
| GraphQL API and prb CLI | No | No | Partly | No | Partly |
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | You describe the job. The agent reads and updates your Probo records and uses Gmail, Slack and 62 other apps in the same run. | Marketing teams logging tools, campaigns and privacy requests without learning Probo. | 65 apps, not thousands. Invites, signature requests and publishing stay in Probo. |
| Probo MCP server | Probo's own MCP server lets AI clients such as Claude, Cursor and VS Code read and change your records. | Compliance leads working in Probo while they chat. | Scheduling depends on your AI client, and other apps need their own connectors. |
| n8n community node | A Probo node for n8n workflows. | Fixed workflows between Probo and other tools. | You build and fix each workflow yourself. |
| Probo webhooks | Probo sends signed events when vendors, users, documents, tasks, obligations or privacy requests change. | Teams with their own code to receive events. | Risks, controls and audits send no events. |
| GraphQL API and prb CLI | Developers script Probo with a scoped token, or run the prb command line tool in a CI pipeline. | Engineering and security teams. | Needs someone to write and run the scripts. |
Connect Probo once. After that, you describe each job in plain English.
Allow all read operations once per app; approve each kind of write once.
A schedule starts the job, or you do by asking.
In Probo, open your account menu, go to OAuth tokens and create a token with read and write scopes for the records your jobs use.
Add the token and your Probo organization id in Letaido. Both go on one connection.
Allow all read operations once per app; approve each kind of write once. Then save it to repeat.
117 actions across vendors, privacy records, risks, controls, documents and tasks.
In Probo, open your account menu, go to OAuth tokens and create a scoped access token. Paste it into Letaido with your organization id. Give the token write scopes for the records your jobs change, such as third parties.
Yes. Probo runs its own MCP server for AI clients such as Claude, Cursor and VS Code. Letaido is not an MCP server. It has its own Probo connector, mixes Probo with Gmail and Slack, and runs jobs on a schedule or when you ask.
No. Actions that make Probo send email, such as invites, signature requests and publishing with approvers, are switched off. Letaido can draft documents and update records, and you send from Probo.
No. Probo jobs run on a schedule, like the Monday privacy requests post, or when you ask.
Probo Cloud in the EU region. If your organization is on the US region or self-hosted, check with Letaido before you connect.
Allow all read operations once per app; approve each kind of write once.
Connect Probo, then ask for a job like "Add our new marketing tool to Probo's vendor list". Leta gets it done on your schedule, or the moment you ask.
Get LetaidoFetch and list documents, document versions, and their content across the organization.
Create documents, open and edit draft versions, set default approvers, and archive or unarchive documents.
View signatures on document versions and cancel open signature requests.
Create, read, update, delete, and link risks in the risk register, including their connections to measures, documents, and obligations.
Create, read, update, delete, and link controls and measures, including their relationships to documents, audits, and third parties.
Create, read, update, delete, and link audits and findings, including audit reports and finding-audit relationships.
Create, read, update, and delete tasks, and list tasks by organization or by measure.
Add, update, delete, and vet vendors, run risk assessments against them, and list all third-party records.
Create, read, update, and delete processing activities, data types, DPIAs, TIAs, and rights requests in the data register and RoPA.
Create, read, update, and delete obligations and track their links to risks and controls.
Add, view, update, and delete assets in the asset register.
Create, read, update, and delete Statements of Applicability and their per-control rows.
Create, update, deactivate, and remove user profiles and manage organization roles.