Get person with the Salesloft API
Returns one person, with contact details, owner, account and the counts of emails and calls.
- Identifier
- salesloft_get_person
The request
POST https://connect.reportei.com/api/tools/salesloft_get_person/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"id": "<id>"
}
}Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | Yes | Id of the person, from List people or Create person. |
Supported connections
Your customer connects their Salesloft account once, with one of the modes below. The same connection serves every tool of the toolkit.
OAuth with your product's app
You register your product's OAuth app once, with POST /api/merchants/credentials/salesloft, and your customer authorizes the account on a consent screen. Connect renews the token when it is about to expire.
The response
On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.
Ready for AI agents
This tool's input is a JSON Schema, available at GET /api/tools/salesloft_get_person. It becomes your agent's tool definition with no conversion.
Other Salesloft tools
- List peopleGETLists the people of the team, 25 per page by default, optionally filtered by email address, name or current cadence. Paginate with page, starting at 1, and per_page, up to 100; the next_page of the response metadata is null on the last page.
- Create personPOSTCreates a person. Send email_address, or phone together with last_name, because one of them identifies the person on the team; an email address already on the team is refused.
- Update personPUTUpdates the given fields of a person.
- List cadencesGETLists the cadences the user can see, 25 per page by default. Use the id of a cadence in the membership and activity tools. Paginate with page, starting at 1, and per_page, up to 100.
- List cadence membershipsGETLists who is or was on a cadence. Each membership links a person to a cadence, with its current state and counts, and has the id that Delete cadence membership takes. Filter by person_id or cadence_id.
- Create cadence membershipPOSTAdds a person to a cadence, on the first step, for the connected user. The person and the cadence must be visible to the user, a personal cadence must be the user's own, and a person with do_not_contact cannot be added.
- Delete cadence membershipDELETERemoves a person from a cadence by deleting the membership.
- List emailsGETLists the emails of the team, sent or scheduled, with status, the counts of views, clicks and replies, and the person, cadence and step of each. Paginate with page, starting at 1, and per_page, up to 100.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
