Tasks
This table has 1 row per task and per org id.
Note: for the purpose of metrics, tasks may be duplicative. Calls and calls tasks will be related, as will Mailings and mailing tasks.
| Column | Type | Definition | Sample Value(s) | Sample Use |
|---|---|---|---|---|
| ACCOUNT_ID | Varchar | The associated account ID for the task. | Maps to the ACCOUNTS table | |
| ACTION | Varchar | The action type of the task. Can be 'action_item', 'call', 'email', or 'in_person'. | 'action_item', 'call', 'email', 'in_person' | |
| AUTOSKIP_AT | Timestamp_NTZ | The UTC datetime for when the task was skipped. | ||
| BENTO | Varchar | A collection of machines that power the Outreach app. Orgs live inside these. | This may distinguish orgs that are in different data centers. | |
| CALL_ID | Varchar | If a call occurs in regards to a task, it is mapped here. | Maps to the CALLS table | |
| COMPLETER_ID | Varchar | The user that completed the task. | Maps to the USERS table | |
| CREATED_AT | Timestamp_NTZ | The UTC datetime that the task was completed. | ||
| CREATOR_ID | Varchar | The ID for whomever created a record in Outreach, or who updated it if records are overwritten when changed. Maps to different tables based on the "creator_type" field. | ||
| CREATOR_TYPE | Varchar | The object type that created this row. | 'plugin', 'app', 'user', 'trigger', 'import' | This will dictate what table the creator_id maps to. |
| DML_AT | Timestamp_NTZ | A datetime (local to server) in which the row was last modified. dml_at can be used to identify updated and new records, but as tables may not see changed records every day, it is not authoritative on when the table was last synced. | 2019-01-01 12:14:01:10 | Where dml_at::date >= current_date-7 This will return all rows modified in the last 7 days. |
| DML_TYPE | Varchar | The type of manipulation that last occurred to a row. | 'update', 'delete', 'insert', 'backfill', 'backfill-delete' | Where dml_type <> 'delete' Excludes deleted rows. |
| DUE_AT | Timestamp_NTZ | The UTC datetime for when a task is due. | ||
| ID | Varchar | Represents an individual row of data in a table. Fields in other tables that match to this ID will be called thisTable_id. e.g. ID in the calls table will appear as the call_id in another table. | Count(1), count(id), and count(distinct id) are equivalent in a table without joins or groupings for a given bento & o_id. | |
| IS_DELETED_IN_APP | Boolean | Is the latest dml_type "delete" or "backfill-delete". | Where is_deleted_in_app = false Only keeps undeleted rows. | |
| MAILING_ID | Varchar | If a mailing is sent, it is mapped here. | Maps to the MAILINGS table | |
| NOTE | Varchar | Any notes associated with the task, either manual or from a sequence step. | ||
| OPPORTUNITY_ID | Varchar | If a task is associated with an opportunity ID, it will be mapped here. | Maps to the OPPORTUNITIES table | |
| OWNER_ID | Varchar | The user responsible for the task. | Maps to the USERS table | |
| O_ID | Varchar | Organization ID, also called instance ID. This is the ID for your unique Outreach account. | Most commonly used on joins alongside other primary keys. where a.o_id = b.o_id and a.id = b.a_id | |
| PROSPECT_ID | Varchar | The associated prospect ID for the task. | Maps to the PROSPECTS table | |
| SCHEDULED_AT | Timestamp_NTZ | The date and time the pending task is scheduled for. | ||
| SEQUENCE_ID | Varchar | The associated sequence ID for the task. | Maps to the SEQUENCES table | |
| SEQUENCE_STATE_ID | Varchar | The associated sequence state ID for the task. | Maps to the SEQUENCE_STATES table | |
| SEQUENCE_STEP_ID | Varchar | The associated sequence step ID for the task. | Maps to the SEQUENCE_STEPS table | |
| STATE | Varchar | The current state of the task. | 'incomplete' , 'complete', 'skipped' | |
| STATE_CHANGED_AT | Timestamp_NTZ | The UTC datetime for when the task's state was last changed. | ||
| SURROGATE_ID | Varchar | An md5 hash of bento, o_id and ID for a table. | This can be used to get distinct counts of records if an account has more than 1 org instance. Two orgs will both have a prospect with ID of "1" but each will have a different surrogate ID. | |
| TASK_PRIORITY_ID | Varchar | Maps to a tasks priority. With increasing integer values reflecting higher urgency. | Maps to the TASKS_PRIORITY table | |
| TASK_THEME_ID | Varchar | Maps to a tasks theme or purpose. | Maps to the TASKS_THEME table | |
| TASK_TYPE | Varchar | The type of task. Can be 'follow_up', 'manual', 'no_reply', 'sequence_open', 'sequence_click', 'sequence_step_call', 'sequence_step_email', 'sequence_step_linkedin_interact_with_post', 'sequence_step_linkedin_other', 'sequence_step_linkedin_send_connection_request', 'sequence_step_linkedin_send_message', 'sequence_step_linkedin_view_profile', 'sequence_step_sms', 'sequence_step_task', or 'touch'. Tasks created through the API will automatically be 'manual' tasks. | 'follow_up', 'manual', 'no_reply', 'sequence_open', 'sequence_click', 'sequence_step_call', 'sequence_step_email', 'sequence_step_linkedin_interact_with_post', 'sequence_step_linkedin_other', 'sequence_step_linkedin_send_connection_request', 'sequence_step_linkedin_send_message', 'sequence_step_linkedin_view_profile', 'sequence_step_sms', 'sequence_step_task', 'touch' | |
| TEMPLATE_ID | Varchar | Any associated templates for mailings to be sent with for this task. | Maps to the TEMPLATES table | |
| UPDATED_AT | Timestamp_NTZ | The UTC datetime for the last time this record was updated. | 2019-01-01 20:14:01:10 | Almost equivalent to dml_at (but adjusted for time zones), but doesn't include record creation or deletion. |
| UPDATER_ID | Varchar | Same as creator_id above, but refers to who last did the update of the record. |