List tasks with the Agendor API

Lists the tasks and activities the user can see, 10 per page by default, in data. Without entityType and entityId, createdByUserId or sortBy, the call needs dueDateGt, createdDateGt or updatedDateGt, at most 31 days before the matching upper bound, or before today when there is none.

Identifier
agendor_list_tasks

The request

POST https://connect.reportei.com/api/tools/agendor_list_tasks/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "entityType": "deal"
  }
}

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

ParameterTypeRequiredDescription
entityTypestringNoKind of record whose tasks are returned. Goes together with entityId.Values: deal, person, organization
entityIdintegerNoId of the record, from List deals, List people or List organizations, matching entityType.
finishedEqstringNotrue returns only finished tasks, false only open ones.Values: true, false
dueDateGtstringNoReturns tasks due on or after this date and time, in ISO 8601.
dueDateLtstringNoReturns tasks due on or before this date and time, in ISO 8601.
createdDateGtstringNoReturns tasks created on or after this date and time, in ISO 8601.
updatedDateGtstringNoReturns tasks updated on or after this date and time, in ISO 8601.
createdByUserIdintegerNoId of the user who created the tasks, from List users.
sortBystringNoDate used to sort the results.Values: createdAt, updatedAt, dueDate, finishedAt
sortOrderstringNoSort direction. Only with sortBy.Values: asc, desc
pageintegerNoPage number, starting at 1.
per_pageintegerNoTasks per page, up to 100. The default is 10.

Supported connections

Your customer connects their Agendor account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

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/agendor_list_tasks. It becomes your agent's tool definition with no conversion.

Other Agendor tools

See all 15 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.