CRM & deals
An AI agent that keeps your Pipedrive pipeline honest.
Connect Pipedrive and an OpenHelm agent can watch your deals, chase the ones going quiet, log researched context, and send the team a weekly state-of-the-pipeline email, on a schedule you approve once and then leave running.
What agents do with Pipedrive. Recurring jobs, checked every run.
Weekly pipeline email
Each week, summarise deals won, lost and stalled, with the three deals most in need of attention and why.
Quiet-deal chaser
Identify deals with no activity beyond your threshold and draft a tailored follow-up for each, ready for the owner to send.
Lead research notes
When new leads arrive, research the company with a real browser and attach a short, source-cited note so the first call starts warm.
Lost-deal pattern review
Monthly, read lost-deal reasons and produce a short trends report into a data table you can track quarter over quarter.
Connect Pipedrive. A few minutes, once.
Connect Pipedrive
Add Pipedrive under Connections in the OpenHelm app and paste a scoped API key, or provision it programmatically with POST /v1/connections.
Describe the job in plain English
Tell OpenHelm what you want done and how often. It drafts a plan with a schedule, the tools it will use, and a clear definition of done.
Approve the plan
No job fires until you have reviewed the plan. Set the autonomy level to control whether writes execute directly or queue for your approval.
It runs, self-checks and reports
Runs execute in isolated cloud sandboxes on schedule. An independent evaluator scores each run against the goal, and results arrive as logs, emails or data-table rows.
Or provision it over the API (see the Connections API docs):
curl https://api.openhelm.ai/v1/connections \
-H "Authorization: Bearer oh_live_..." \
-H "Content-Type: application/json" \
-d '{ "name": "Pipedrive", "type": "token", "secret": "<your Pipedrive API key>" }'
# The secret is write-only: stored encrypted, injected only at run time.Questions
What does the agent need access to?
A Pipedrive API token, stored encrypted and injected only at run time. You can scope what jobs do with it, see every call in the run log, and rotate or delete the token whenever you like.
How does OpenHelm connect to Pipedrive?
With a scoped API key: create one in Pipedrive, paste it into Connections in the OpenHelm app, or provision it programmatically with POST /v1/connections. The key is stored encrypted and injected only at run time inside an isolated sandbox, and you can rotate or delete it whenever you like.
Can the jobs run on a schedule without me?
Yes, that is the point. Jobs run once, on an interval, or on a cron expression. A scheduler fires them, a watchdog times out anything hung, and a separate evaluator checks each run actually advanced the goal. You approve the plan before anything runs for the first time.
Is my Pipedrive data safe?
Each run executes in an isolated cloud sandbox with scoped, revocable credentials and no middle-layer copy of your data. Every action is logged per run, results come back with evidence, and the agent never fabricates data it could not verify.
More in CRM & deals
Give your product a team that never clocks off.
Start free in the browser, or run it on your Mac with your own Claude Code or Codex plan.