Nooks: List Tasks

List tasks.

Tool ID: nooks_list_tasks

Run this action

This action has conditional or dynamic input fields that cannot be represented by a reliable static example. Inspect the live contract before executing it:

deepline tools get nooks_list_tasks --json

Example response

The static output schema is not detailed enough to generate a reliable example. Use deepline tools get nooks_list_tasks --json for the complete live contract.

Input reference

Returns a paginated list of tasks. Tasks represent individual outreach activities (calls, emails, etc.) assigned to users. Example: bash curl -X GET 'https://partner-api.nooks.in/v1/tasks?page[size]=50' \ -H "Authorization: Bearer nooks-api-..." Filter by prospect:

bash curl -X GET 'https://partner-api.nooks.in/v1/tasks?filter[prospect][id]=770e8400-e29b-41d4-a716-446655440003' \ -H "Authorization: Bearer nooks-api-..."

Filter by action type:

bash curl -X GET 'https://partner-api.nooks.in/v1/tasks?filter[action]=call,manual_email' \ -H "Authorization: Bearer nooks-api-..."

Filter by sequence:

bash curl -X GET 'https://partner-api.nooks.in/v1/tasks?filter[sequence][id]=550e8400-e29b-41d4-a716-446655440000' \ -H "Authorization: Bearer nooks-api-..."

Filter by account (joins through the task’s prospect): ```bash curl -X GET See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.page`	`object`	No	—	Number of items per page (max 100)
`payload.filter`	`object`	No	—	Filter by IDs (comma-separated UUIDs). An empty value is treated as “no filter”.
`payload.include`	`array`	No	—	Comma-separated relations to expand inline. Valid values: `owner`, `prospect`, `sequence`, `sequenceState`, `sequenceStep`. Max 3. Maximum items: 3.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.data`	`array`	No	—	—
`result.data.data[].id`	`string`	Yes	—	Unique identifier for the task Format: `uuid`.
`result.data.data[].action`	`"call" \| "manual_email" \| "auto_email" \| "manual_email_reply" \| "auto_email_reply" \| "basic_task" \| "linkedin_connection_request" \| "manual_linkedin_connection_request" \| "manual_linkedin_message" \| "automatic_linkedin_message" \| "manual_sms" \| "auto_sms"`	Yes	—	Type of action for this task: - `call`: Phone call task - `manual_email`: Manually composed email - `auto_email`: Automatically sent email - `manual_email_reply`: Manual email reply - `auto_email_reply`: Automatic email reply - `basic_task`: Generic manual task - `linkedin_connection_request`: LinkedIn connection request - `manual_linkedin_connection_request`: Manual LinkedIn connection request - `manual_linkedin_message`: Manual LinkedIn message - `automatic_linkedin_message`: Automatically See the live schema for the complete constraint.
`result.data.data[].completed`	`boolean`	Yes	—	Whether the task has been completed
`result.data.data[].dueAt`	`string`	Yes	—	When the task is due Format: `date-time`.
`result.data.data[].note`	`string \| null`	Yes	—	Optional note or instructions for the task
`result.data.data[].status`	`string \| null`	Yes	—	Current status of the task (pending, ready, finished, skipped, failed)
`result.data.data[].priority`	`"low" \| "normal" \| "high" \| "urgent"`	Yes	—	Priority level of the task Allowed: `low`, `normal`, `high`, `urgent`.
`result.data.data[].owner`	`object`	Yes	—	A reference to a related resource
`result.data.data[].owner.id`	`string`	Yes	—	Unique identifier of the referenced resource
`result.data.data[].owner._href`	`string`	Yes	—	API path to the referenced resource
`result.data.data[].prospect`	`object`	Yes	—	A reference to a related resource
`result.data.data[].prospect.id`	`string`	Yes	—	Unique identifier of the referenced resource
`result.data.data[].prospect._href`	`string`	Yes	—	API path to the referenced resource
`result.data.data[].sequence`	`object \| null`	Yes	—	A reference to a related resource
`result.data.data[].sequence.id`	`string`	Yes	—	Unique identifier of the referenced resource
`result.data.data[].sequence._href`	`string`	Yes	—	API path to the referenced resource
`result.data.data[].sequenceState`	`object \| null`	Yes	—	A reference to a related resource
`result.data.data[].sequenceState.id`	`string`	Yes	—	Unique identifier of the referenced resource
`result.data.data[].sequenceState._href`	`string`	Yes	—	API path to the referenced resource
`result.data.data[].sequenceStep`	`object \| null`	Yes	—	A reference to a related resource
`result.data.data[].sequenceStep.id`	`string`	Yes	—	Unique identifier of the referenced resource
`result.data.data[].sequenceStep._href`	`string`	Yes	—	API path to the referenced resource
`result.data.data[].createdAt`	`string`	Yes	—	When the task was created Format: `date-time`.
`result.data.data[].updatedAt`	`string`	Yes	—	When the task was last updated Format: `date-time`.
`result.data.links`	`object`	No	—	Pagination links for navigating through results. Links are returned as relative references (path + query) that should be resolved against the base URL of the request.
`result.data.links.first`	`string`	No	—	URL for the first page Format: `uri-reference`.
`result.data.links.prev`	`string \| null`	No	—	URL for the previous page (null if on first page) Format: `uri-reference`.
`result.data.links.next`	`string \| null`	No	—	URL for the next page (null if on last page) Format: `uri-reference`.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Nooks: List Tasks

Run this action

Example response

Input reference

Output reference

Deepline cost

​Run this action

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

Example response

Input reference

Output reference

Deepline cost

Related documentation