Send chatbot leads to Account Engagement (Pardot)
A prospect in the business unit you name
A lead from the chat becomes a prospect in the Account Engagement business unit you name -- named, rather than assumed, because the API refuses anything else and says so in a way that reads like a bad token.
What it does
The business unit is part of the connection
Without it the API answers 401 Access Denied, which looks like a credential problem. We ask for the tenant's eighteen-character id and check its shape on the form.
Standard and custom prospect fields
The standard fields are there from the start, and your custom fields are read from the account and offered by their API name.
The same connected app as Salesforce
Account Engagement logs in through Salesforce, so the app you already made is the one this uses.
How to connect it
Read the full guide- 1
Use your Salesforce connected app
The same consumer key, secret and refresh token, with the pardot_api scope.
- 2
Find your business unit id
Salesforce Setup, Account Engagement Setup, Business Unit Setup. Eighteen characters, not fifteen.
- 3
Connect Account Engagement
Paste the five values.
- 4
Map the fields
The email address is required: it is what a prospect is identified by.
Questions people ask
Why does it need the business unit id?
Because the API does. Without the header it refuses with Access Denied, and with a fifteen-character id it refuses again with a message naming the length.
Can it add the prospect to a list?
Not yet. List membership is a second call and a second decision, and we would rather ask than assume which list.
Does it update an existing prospect?
It creates. Account Engagement identifies prospects by email, so an address it already knows is its own to reconcile.
What teams use it for
Upload your documents, get answers that cite them
One knowledge base, an AI chat or an Ask AI search on any site, and every answer with the passage it came from. Free for 14 days.