LinktLinkt

Tasks

Create and configure workflow templates

A Task defines the configuration for a research workflow. Tasks specify what type of operation to perform and how to execute it.

What is a Task?

Tasks are reusable workflow templates that:

  • Define the type of research operation (search, enrich, monitor)
  • Reference an ICP for targeting criteria
  • Specify configuration parameters
  • Can be executed multiple times to create runs

Task Structure

{
  "id": "507f1f77bcf86cd799439013",
  "name": "Enterprise SaaS Company Search",
  "description": "Search for B2B SaaS companies",
  "flow_name": "search",
  "deployment_name": "main",
  "icp_id": "507f1f77bcf86cd799439011",
  "task_config": {
    "version": "v3.0",
    "config_type": "search-task",
    "desired_contact_count": 1,
    "user_feedback": ""
  }
}

Flow Names

The flow_name field determines what type of workflow the task executes:

Flow NamePurposeConfig Type
searchDiscover new entities matching ICP criteriasearch-task
signal-topicMonitor topics for business signalssignal-topic
signal-csvGenerate signals from uploaded CSV datasignal-csv
signal-sheetMonitor existing sheet entities for signalssignal-sheet
ingestImport and enrich entities from CSV filesingest-task

Task Configurations

Each flow type requires a specific configuration structure. The config_type field must match the flow.

Search Task Configuration

For discovering new companies matching your ICP:

{
  "version": "v3.0",
  "config_type": "search-task",
  "desired_contact_count": 1,
  "user_feedback": ""
}
FieldTypeDescription
versionstringConfiguration version (use v3.0)
config_typestringMust be search-task
desired_contact_countintegerNumber of contacts to find per company (0 for companies only)
user_feedbackstringOptional feedback to refine search results
webhook_urlstringOptional HTTPS URL for completion notifications (see Webhooks)

Signal Topic Configuration

For monitoring topics across the web for business signals:

{
  "version": "v1.0",
  "config_type": "signal-topic",
  "topics": ["AI funding", "Series B"],
  "signal_types": ["funding", "leadership_change"]
}
FieldTypeDescription
config_typestringMust be signal-topic
topicsarrayKeywords and phrases to monitor
signal_typesarrayTypes of signals to detect
webhook_urlstringOptional HTTPS URL for completion notifications (see Webhooks)

Signal CSV Configuration

For generating signals from uploaded CSV data:

{
  "version": "v1.0",
  "config_type": "signal-csv",
  "file_id": "507f1f77bcf86cd799439030",
  "signal_types": ["funding", "product_launch"]
}
FieldTypeDescription
config_typestringMust be signal-csv
file_idstringID of uploaded CSV file (see Files)
signal_typesarrayTypes of signals to detect
webhook_urlstringOptional HTTPS URL for completion notifications (see Webhooks)

Signal Sheet Configuration

For monitoring existing entities in a sheet for signals:

{
  "version": "v1.0",
  "config_type": "signal-sheet",
  "sheet_id": "507f1f77bcf86cd799439012",
  "signal_types": ["funding", "hiring_surge", "leadership_change"]
}
FieldTypeDescription
config_typestringMust be signal-sheet
sheet_idstringID of sheet to monitor
signal_typesarrayTypes of signals to detect
webhook_urlstringOptional HTTPS URL for completion notifications (see Webhooks)

Ingest Task Configuration

For importing and enriching entities from CSV files:

{
  "version": "v1.0",
  "config_type": "ingest-task",
  "file_id": "507f1f77bcf86cd799439030",
  "primary_column": "company_name",
  "csv_entity_type": "company"
}
FieldTypeDescription
config_typestringMust be ingest-task
file_idstringID of uploaded CSV file (see Files)
primary_columnstringCSV column containing entity identifier
csv_entity_typestringType of entities in CSV (company or person)
webhook_urlstringOptional HTTPS URL for completion notifications (see Webhooks)

Configuration Versioning

Task configurations use semantic versioning. Always use the latest stable version:

Config TypeCurrent Version
search-taskv3.0
signal-topicv1.0
signal-csvv1.0
signal-sheetv1.0
ingest-taskv1.0

Task Execution

When you execute a task, a Run is created to track the execution. The run contains:

  • Status updates as the workflow progresses
  • Results including discovered entities or signals
  • Resource usage metrics (credits, entities created)

See Runs for details on monitoring execution.

Next Steps

  • Runs - Monitor task execution
  • Webhooks - Receive completion notifications
  • ICPs - Define targeting criteria
  • Signals - Understanding signal outputs
  • API Reference - Complete task endpoint documentation

On this page