Skip to main content
GET
List follow-up tasks
Returns your team’s follow-up tasks for every rep, newest first, one page at a time. Tasks come from two places:
  • Salesfinity’s AI reviews logged calls and creates a task when it recommends following up, with a date and what it learned on the call. These tasks have priority medium and no context.
  • Reps create tasks from a call themselves, with their own priority and notes in context. The AI then adds what it learned on the call.

Example

contact and company hold the full contact and company records, not IDs, and are null if the record no longer exists. Records can carry more fields than the example shows. user is the assigned rep’s ID as a string. The response schema on this page shows these three fields differently; the example is what production returns.

Status and touches

  • status is not_overdue until follow_up_date passes. A job that runs every 10 minutes then sets it to overdue, so it can lag by up to 10 minutes. completed means the rep finished the task.
  • touches counts the calls logged to the contact while the task was open.
  • The AI fills tags, point_of_view, use_cases, mentioned_people, existing_solution_name, existing_solution_issues and satisfaction_with_existing_solution from the call. Any of them can be empty or absent.

Filtering, sorting and paging

  • There are no filters. To find one rep’s overdue tasks, page through every task and filter on user and status yourself. Archived tasks are included; check is_archived. A query parameter other than page, limit and sort fails with 400.
  • sort accepts several comma-separated fields, such as follow_up_date,-createdAt. priority sorts alphabetically (high, low, medium), not by urgency.
  • limit defaults to 10. Above 100 is treated as 100, and pagination.limit says what was used. Request pages with page until pagination.next is null.

Errors

Authorizations

x-api-key
string
header
required

Team-scoped API key generated in the Salesfinity dashboard under Settings → Connections → API & Webhooks. A missing or invalid key returns HTTP 403.

Query Parameters

page
integer
default:1

Page number, starting at 1.

Required range: x >= 1
limit
integer

Tasks per page. Default 10. Above 100 is treated as 100; below 1 fails with 400.

Required range: 1 <= x <= 100
sort
string

Comma-separated fields to sort by, such as follow_up_date or -createdAt. Prefix a field with - for descending. Defaults to -createdAt.

Example:

"follow_up_date,-createdAt"

Response

One page of follow-up tasks.

data
object[]
pagination
object