Connect your CRM

Use this when your CRM isn’t one of our ready-made integrations. Your CRM keeps Sales Ask’s calendar up to date, and Sales Ask returns the outcome of every recorded conversation to your CRM.

Before you build, make sure you have:

your organization API key
the custom CRM integration turned on for your organization: email support@salesask.com, and tell us whether to match recordings by time or by location
every rep added to Sales Ask with the same email address they use in your CRM

Send appointments

Call the API from each place your CRM creates, edits, or deletes an appointment, so Sales Ask always has the same schedule as your CRM.

In your CRM	Call
Appointment created	`POST /v1/scheduled-tasks`
Appointment rescheduled, reassigned, or edited	`POST` again with the same `event_id`, or `PUT /v1/scheduled-tasks/{event_id}`
Appointment cancelled or deleted	`DELETE /v1/scheduled-tasks/{event_id}`

POST creates the appointment, or updates it when Sales Ask already has that event_id. You can send the full appointment every time it changes.

Appointment fields

string

required

Your CRM’s ID for the appointment. Send it as a string. You use it to update or delete the appointment, and it comes back in every webhook.

string

required

Email of the rep who owns the appointment. It must match a member of your Sales Ask organization.

string

required

Start time in UTC, ending in Z or +00:00, for example 2026-03-01T14:00:00.000Z. Other offsets and Unix timestamps are rejected.

string

End time in UTC.

string

Appointment title, shown to the rep.

object

The customer the appointment is with.

Show customer fields

string

Your CRM’s customer ID. Strongly recommended: Sales Ask uses it to group every recording for the same customer into one Client, and to tell appointments apart when matching.

string

Customer name, shown in the rep’s reminders and app.

string

Customer email, saved on the Client.

string

Appointment address. Required if you match recordings by location.

Any other fields, such as phone numbers or notes, are ignored.

Examples

Create
Reschedule
Cancel
Look up

curl -X POST https://integrations.salesask.com/v1/scheduled-tasks \
  -H "x-api-key: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "event_id": "APPT-9871",
    "user_email": "rep@yourcompany.com",
    "start_time": "2026-03-01T14:00:00.000Z",
    "end_time": "2026-03-01T15:00:00.000Z",
    "title": "Design consultation",
    "customer": {
      "id": "CUST-123",
      "name": "John Doe",
      "email": "john@example.com",
      "location": "123 Main St, Austin, TX 78701"
    }
  }'

Sales Ask returns 201 with the saved appointment, whether it was new or updated:

{
  "appointment": {
    "id": "task_abc123",
    "event_id": "APPT-9871",
    "user_email": "rep@yourcompany.com",
    "startTime": "2026-03-01T14:00:00.000Z",
    "endTime": "2026-03-01T15:00:00.000Z",
    "title": "Design consultation",
    "client": {
      "id": "CUST-123",
      "name": "John Doe",
      "email": "john@example.com",
      "location": "123 Main St, Austin, TX 78701"
    },
    "scheduledAt": "2026-03-01T13:45:00.000Z",
    "status": "scheduled",
    "createdAt": "2026-02-28T09:00:00.000Z",
    "updatedAt": "2026-02-28T09:00:00.000Z"
  }
}

Send only what changed. Fields inside customer are merged with what Sales Ask already has.

curl -X PUT https://integrations.salesask.com/v1/scheduled-tasks/APPT-9871 \
  -H "x-api-key: <YOUR_API_KEY>" \
  -H "Content-Type: application/json" \
  -d '{
    "start_time": "2026-03-01T16:00:00.000Z",
    "end_time": "2026-03-01T17:00:00.000Z"
  }'

A new start time reschedules the rep’s reminders.

curl -X DELETE https://integrations.salesask.com/v1/scheduled-tasks/APPT-9871 \
  -H "x-api-key: <YOUR_API_KEY>"

The appointment leaves the rep’s list and its reminders stop. A second delete returns 404, so retries are safe.

One appointment:

curl https://integrations.salesask.com/v1/scheduled-tasks/APPT-9871 \
  -H "x-api-key: <YOUR_API_KEY>"

A rep’s appointments for a month:

curl "https://integrations.salesask.com/v1/scheduled-tasks?user_email=rep@yourcompany.com&fromDate=2026-03-01&toDate=2026-03-31" \
  -H "x-api-key: <YOUR_API_KEY>"

The list returns appointments, nextCursor, and hasMore. Pass nextCursor as startAfter for the next page. limit is 1 to 100 (default 25). fromDate and toDate filter on scheduledAt, the next reminder time, which is up to 15 minutes before the start, so widen the range slightly.

If a request fails

Status	Cause
`400`	A required field is missing (the response names it in `field`), a time isn’t UTC, or `user_email` isn’t a member of your organization.
`401`	The API key is missing or wrong.
`404`	No appointment with that `event_id`.

How Sales Ask uses your appointments

	What Sales Ask does	What it needs from you
Linking recordings by time	Links the recording to the rep’s appointment whose start is closest to when recording began, within one hour either side. An appointment at 2:00 PM and a recording started at 2:05 PM are linked.	`user_email`, `start_time`
Linking recordings by location	Links the appointment whose address is within 250 meters of the rep, among appointments within three hours. Falls back to time if none is close enough.	`customer.location`
Reminders to record	Sends the rep two push notifications with the customer’s name: about 15 minutes before (Mic Check: Ready to Record in 15 mins?) and at the start time (Mic Check: Ready to Record?).	A start time in the future, and the rep signed in to the mobile app with notifications on
A Client for each customer	When a linked recording is processed, finds or creates a Client and adds the recording to it, so every meeting with the same buyer builds one profile.	`customer.id`

The link between a recording and an appointment is how your event_id gets back to you, so keep appointments current when they move. When two appointments are equally close, Sales Ask lets the rep choose. Reps can also pick or change the appointment themselves. The app shows each rep’s appointments from the past 30 days and the next 7.

Get results back

Sales Ask doesn’t write into your CRM. It posts each result to a URL you choose, and your CRM saves it.

Add a webhook

Create it

In Sales Ask, go to Settings → Webhooks, add a webhook, and enter your endpoint URL. Set Trigger to All Sources.

Pick events

Under Events, select the events below. Most integrations select all three.

Choose extracted fields (optional)

Under Custom Payloads, add what Sales Ask should pull from each conversation, such as budget, design preferences, or reason to buy.

Turn it on

Make sure the webhook is Active, and save.

Event	Sent when
`recording.processed`	A recording finishes processing.
`recording.integration_updated`	A rep links a recording to an appointment, or changes the link, after processing. Same payload as `recording.processed`.
`client.created`	A rep creates a new client in Sales Ask, such as a walk-in, and records with them.

For a recording with a client the rep created in Sales Ask, you get client.created instead of recording.processed. Subscribe to both to hear about every recording.

What you receive

{
  "event": "recording.processed",
  "data": {
    "id": "rec_abc123",
    "name": "Design consultation with John Doe",
    "notes": "Buyer is relocating for work and wants to move in by August...",
    "actionItems": "Action items from meeting\n- Send lot pricing\nClient action items\n- Share pre-approval letter",
    "meetingUrl": "https://app.salesask.com/meetings/rec_abc123",
    "process": {
      "answers": [
        { "question": "Did the rep ask about timeline?", "answer": "Yes" }
      ],
      "summary": "Rep covered timeline and budget, but didn't book a follow-up."
    },
    "processFollowed": 3,
    "processMissed": 1,
    "processTotal": 4,
    "integration": {
      "type": "custom",
      "entity": {
        "eventId": "APPT-9871",
        "entityId": "CUST-123",
        "entityName": "John Doe",
        "client": {
          "id": "CUST-123",
          "name": "John Doe",
          "email": "john@example.com",
          "location": "123 Main St, Austin, TX 78701"
        },
        "appointmentDate": "2026-03-01T14:00:00.000Z",
        "title": "Design consultation",
        "userEmail": "rep@yourcompany.com"
      }
    },
    "buyerProfile": {
      "budget": { "value": "$450,000 to $500,000", "reason": "Buyer said they're pre-approved up to $500k." },
      "reasonToBuy": { "value": "Relocating for a new job", "reason": "Starts work in Austin in July." }
    }
  }
}

string

The event_id you sent. Use it to find the appointment in your CRM. If data.integration is null, the recording wasn’t linked to an appointment.

object

The customer you sent with the appointment. For client.created, entity holds what the rep entered instead, such as name, email, design, and community.

string

AI notes and action items, as plain text.

object

Your sales process questions, the rep’s answers, and a summary. processFollowed, processMissed, and processTotal count them. critical_step holds the answer to your critical step question, if you have one.

object

Each group you set up under Custom Payloads has its own key, such as buyerProfile above.

string

Link to the recording in Sales Ask. For the transcript and audio, call GET /v1/recordings/{id} and GET /v1/recordings/{id}/transcript.

Handling deliveries

Verify the sender: every webhook carries your organization API key in the x-api-key header. Reject requests where it doesn’t match.
Reply within 10 seconds with any 2xx status, and do slow work afterwards. Don’t redirect.
No retries: a missed delivery isn’t sent again. Fetch the recording with GET /v1/recordings/{id} to catch up.
Automatic shut-off: a 410 response turns the webhook off at once, and repeated 404s over three days do too. Turn it back on in Settings → Webhooks.

Go-live checklist

Send a test appointment

Create an appointment for a rep about 20 minutes from now. Check that it shows in their app and the reminder arrives.

Record against it

Have the rep record a short conversation at the appointment time.

Check the webhook

When processing finishes, confirm your endpoint got recording.processed with your event_id in data.integration.entity.eventId.

Clean up

Delete the test appointment with DELETE /v1/scheduled-tasks/{event_id}.

To test your endpoint without recording, click the test button on the webhook in Settings → Webhooks. You can also call POST /v1/webhooks/test with url and a processed recording object from GET /v1/recordings/{id}. GET /v1/webhooks lists your organization-wide webhooks, but not team webhooks or their events.

Troubleshooting

Recordings aren't linking to appointments

Check that the rep’s Sales Ask email matches the user_email you sent, that the recording started within an hour of the appointment, and that you send customer.id. If you match by location, check customer.location is a full street address.

The webhook never arrives

Check the webhook is Active and subscribed to the event, and that Trigger is All Sources. If the rep created the client in Sales Ask, you get client.created, not recording.processed.

Reps don't get reminders

The rep must be signed in to the mobile app with notifications on, and the appointment must start in the future when you send it.

Still stuck?

Email support@salesask.com with your organization name, the request you sent (without your API key), the response, and the event_id or recording id.

Connect your systems

Working with the API

Integrations

CRMs

Telephony (Dialers)

Other connections

Send appointments

Appointment fields

Examples

If a request fails

How Sales Ask uses your appointments

Get results back

Add a webhook

What you receive

Handling deliveries

Go-live checklist

Troubleshooting

​Send appointments

​Appointment fields

​Examples

​If a request fails

​How Sales Ask uses your appointments

​Get results back

​Add a webhook

​What you receive

​Handling deliveries

​Go-live checklist

​Troubleshooting

Send appointments

Appointment fields

Examples

If a request fails

How Sales Ask uses your appointments

Get results back

Add a webhook

What you receive

Handling deliveries

Go-live checklist

Troubleshooting