LiveCRMSends call data

PyAI x Salesforce

Recap writes back to the record your team actually works in.

You pick the object and the fields; PyAI fills them after every call. A configurable field map writes Recap outputs (TL;DR, summary, next steps, your extracted fields) onto the Salesforce record your calls reference, and an optional follow-up Task carries the TL;DR and summary so nothing waits on a human typing it up.

Connect Salesforce Read the docs

Status: Live
Direction: PyAI to Salesforce
Setup: Console, no code
Cost: Included

What lands in Salesforce

Two writes per call, both optional and configurable: a field update on the record your call references, and a Task with the TL;DR as subject and the summary as the body.

A field map and the resulting Task

Field map (yours to define):
  tldr        -> Description
  summary     -> Call_Summary__c
  next_steps  -> Next_Steps__c

Task on the mapped record:
  Subject: Customer asked to reschedule Friday's installation
  Status:  Not Started
  Body:    The customer called to move their appointment...

Setup, end to end

1
Create a connected app in Salesforce and complete the refresh-token flow.
2
In the PyAI console, open Integrations and choose Salesforce, then enter your instance URL, credentials, object, and record-id field.
3
Define the field map: which Recap field writes to which Salesforce field.
4
Save. Every completed call writes back from then on; check the result on the next call's Recap record.

Built into every connection

Delivery you can prove

Verified, and never twice

Every delivery carries proof it is really from us (the X-PyAI-Signature header, an HMAC your tools can verify) and a unique receipt id (the Idempotency-Key), so a retry can never post the same call twice.

Retried, then shown to you

If your endpoint hiccups, we retry with backoff (eight attempts over about twenty minutes). Still failing? The exact error waits on the integration card in your console, not in a log you never read.

Your credentials stay yours

Tokens, secrets, and webhook URLs are encrypted at rest and masked everywhere. They never appear in the messages we send.

Included, no extra fees

Integrations come with your Recap or AMD usage. There is no per-connection or per-delivery charge.

FAQ

Which Salesforce objects can PyAI write to?

Any object your integration user can PATCH: Opportunity, Contact, Account, or a custom object. The call references the record through a CRM field you name (the default is salesforce_id), and the field map decides which fields are updated.

Do I have to create the follow-up Task?

No. Task creation is a toggle in the console. Some teams only want the field update on the record; others want the Task so a rep gets a visible to-do with the TL;DR.

How does the integration sign in?

With your connected app's client id and secret plus a refresh token, all encrypted at rest. PyAI refreshes a short-lived access token per write and never sees or stores your Salesforce password.

What shows me a write failed?

Each Recap record carries a CRM write status (synced, skipped, or the specific failure). A failed write does not affect the summary itself, and the status is visible per call in the console.

Connect Salesforce to PyAI today.

An instant sandbox key lets you test every delivery without billing. Create an account when you want saved projects, and fund a live key for production traffic.

Build with the API Launch an Agent

Agents is live in beta. Sandbox keys have daily limits and never touch billing.