This table has 1 row per meeting (unique meetings gathered from calendar events) and per org id.
|Whether the meeting time was set to all day.
|A collection of machines that power the Outreach app. Orgs live inside these.
|This may distinguish orgs that are in different data centers.
|The prospect ID if booked by calendar extension, otherwise the user who owns the event. In SDR use cases, if this was not booked by a prospect, it is the AE or other individual the SDR booked on behalf of. Booker_ID can equal Creator_ID if booked by an Outreach user on their own behalf.
|Maps to USERS table or PROSPECTS table
|The IDs of the calendars this event is associated with.
|Maps to CALENDARS table
|Whether the meeting has been canceled.
|When the meeting was originally created in Outreach. (This is not the same as external_created_at, when the meeting was originally created/booked in the originating calendar system.)
|The ID of the Outreach user who originally booked the event, or who provided the calendar extension link for a prospect to book on. In SDR use cases, generally the SDR.
|Maps to USERS table
|A string describing the type of individual who originally booked the event.
|The body of the calendar event.
|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.
|Where dml_at::date >= current_date-7 This will return all rows modified in the last 7 days.
|The type of manipulation that last occurred to a row.
|'update', 'delete', 'insert', 'backfill', 'backfill-delete'
|Where dml_type <> 'delete' Excludes deleted rows.
|The time at which the event ends.
|A link to the 3rd party event.
|The created at time in the external system.
|The event ID in the external system.
|The updated at time in the external system.
|The ical ID for this event.
|From the ical spec: "This property defines the revision sequence number of the calendar component within a sequence of revisions."
|A unique ID for this meeting.
|Is the latest dml_type "delete" or "backfill-delete".
|Where is_deleted_in_app = false Only keeps undeleted rows.
|The location specified on the meeting event.
|The time at which the event was marked as no show.
|This link attached to meeting events over the internet, e.g. with Zoom.
|This is a list of any IDs for opportunities that Outreach users have associated with their calendar event for this meeting.
|This may not be comprehensive as it relies on users manually assigning an opportunity to the synced-in calendar event.
|This is a deprecated field. See meeting_attendees to identify the organizer.
|An ID for the Outreach account. This hashed string reflects a specific Outreach app instance within a bento. 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
|True if this is an occurrence of a recurring meeting.
|The external event ID of the recurring event this event is an occurrence of.
|True if this event is marked as private in the 3rd party calendar.
|The source of the event.
|The time the meeting was scheduled to begin.
|An md5 hash of bento, o_id and ID for a table.
|The time at which this meeting was synced from the 3rd party calendar into Outreach.
|The number of attempts that were made to sync an outreach created event to gcal/outlook
|The time the last sync attempt was initiated.
|Title of the meeting.
|The UTC datetime for the last time this record was updated.
|Almost equivalent to dml_at (but adjusted for time zones), but doesn't include record creation or deletion.