Skip to content

CRM & deals

An AI agent for the Salesforce work nobody gets to.

Connect Salesforce and an OpenHelm agent can keep opportunities honest: scheduled pipeline reports, activity-gap chasing, researched account enrichment and hygiene sweeps, all running in the background against your scoped credential.

What agents do with Salesforce. Recurring jobs, checked every run.

  • Pipeline and forecast digest

    Summarise opportunity movement, slipped close dates and coverage against target each week, delivered by email before your pipeline review.

  • Account research briefs

    Ahead of key meetings, research the account with a real browser, combine it with CRM history, and file a one-page brief to the opportunity.

  • No-activity alerts

    Flag open opportunities with no logged activity in a set window and email owners a short list of what needs touching this week.

  • Hygiene exception report

    On a schedule, list records with missing stages, stale next steps or empty amounts into a data table for the ops team to work through.

Connect Salesforce. A few minutes, once.

  1. Connect Salesforce

    Add Salesforce under Connections in the OpenHelm app and complete the hosted sign-in, or mint a connect link programmatically with POST /v1/connections/links.

  2. 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.

  3. 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.

  4. 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):

POST /v1/connections/links
curl https://api.openhelm.ai/v1/connections/links \
  -H "Authorization: Bearer oh_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "provider": "<provider id>", "name": "Salesforce" }'
# Returns a short-lived hosted link. Open it once to authorise,
# then poll GET /v1/connections until it shows as authenticated.

Questions

Does this need a Salesforce admin to set up?

You need a credential with access to the objects the job touches. Most teams connect an integration user with scoped permissions, which takes a few minutes and can be revoked at any time.

How does OpenHelm connect to Salesforce?

Through a scoped OAuth grant: you sign in to Salesforce once via a hosted connect flow, in the OpenHelm app or via a connect link minted with POST /v1/connections/links. OpenHelm stores no passwords, the grant is limited to what your jobs need, and you can revoke it at any time.

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 Salesforce 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.

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.