Salesloft: Calendar Events Upsert Create

Upsert a calendar event.

Tool ID: salesloft_calendar_events_upsert_create

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'salesloft_calendar_events_upsert_create',
  {
    "start_time": "2026-01-15",
    "id": "id_123",
    "i_cal_uid": "example",
    "end_time": "2026-01-15",
    "calendar_id": "calendar_123"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute salesloft_calendar_events_upsert_create --input '{
  "start_time": "2026-01-15",
  "id": "id_123",
  "i_cal_uid": "example",
  "end_time": "2026-01-15",
  "calendar_id": "calendar_123"
}' --json

Example response

The SDK exposes this shape at result.toolResponse.raw. Values below are representative.

{
  "data": {
    "meeting_link": "example",
    "is_performed_by_organizer": true,
    "organizer": "example"
  }
}

Use deepline tools get salesloft_calendar_events_upsert_create --json for the latest machine-readable contract.

Input reference

Upserts a calendar event object. Upsert key is a combination of id and i_cal_uid scoped to the given calendar_id. Bulk operations: This endpoint is used for bulk operations, see bulk jobs for integration instructions. Use calendar/events/upsert as an event type, and this spec as a data spec. This endpoint should be used directly for the time sensitive calendar event updates.

Name	Type	Required	Default	Details
`payload.upsert_key`	`array`	No	—	This parameter customizes the keys used for identifying events in our database. Default: `["id", "i_cal_uid"]`. By default, events are identified based on both :id and :i_cal_uid fields. Example: If `:upsert_key` is set to `["id"]`, events will be identified using :id & :user_guid as keys. This will help prevent creating duplicates in cases where i_cal_uid changes during event updates.
`payload.updated_at`	`string`	No	—	Last modification time of the event in the ISO 8601 format with a time zone offset. The event will not be updated if the ‘updated_at’ timestamp from the payload is earlier than the one in the database. Example: `2022-02-14T10:12:59+00:00`.
`payload.transparency`	`string`	No	—	Transparency of the calendar event. Possible values: `opaque`, `transparent`. Example: `opaque`.
`payload.title`	`string`	No	—	Title of the calendar event
`payload.status`	`string`	No	—	Status of the calendar event. Depending on the status, the calendar event will or will not impact user’s availability. Possible values: `confirmed`, `tentative`, `cancelled`. Example: `confirmed`.
`payload.start_time`	`string`	Yes	—	Start time of the calendar event, as a combined date-time value in the ISO 8601 format with a time zone offset. Example: `2022-02-14T10:12:59+00:00`. Format: `date`.
`payload.recurring`	`boolean`	No	—	Should be set to `true` if this is one of recurring series calendar event.
`payload.recurrence`	`array`	No	—	List of RRULE for a recurring event, as specified in RFC5545. This field is omitted for single events or instances of recurring events. For recurring events, you can optionally include the ‘UNTIL’ key to specify the date/time after which the recurrence rule should stop repeating. The ‘UNTIL’ value must be in UTC and in the format ‘YYYYMMDD’T’HHMMSS’Z’. Example: `["RRULE:FREQ=DAILY;INTERVAL=1;UNTIL=20230731T000000Z"]`
`payload.organizer`	`string`	No	—	Email address of the organizer
`payload.location`	`string`	No	—	Location of the calendar event as free-form text.
`payload.id`	`string`	Yes	—	Id of the calendar event, different for each occurrence in a recurring series. Used as an upsert key.
`payload.i_cal_uid`	`string`	Yes	—	icalUID of the calendar event. Unique identifier for a calendar event across calendars. Used as an upsert key.
`payload.end_time`	`string`	Yes	—	End time of the calendar event, as a combined date-time value in the ISO 8601 format with a time zone offset. Example: `2022-02-14T10:12:59+00:00`. Format: `date`.
`payload.description`	`string`	No	—	Description of the calendar event
`payload.canceled_at`	`string`	No	—	Cancellation time of the calendar event, as a combined date-time value in the ISO 8601 format with a time zone offset. Example: `2022-02-14T10:12:59+00:00`.
`payload.calendar_id`	`string`	Yes	—	Calendar ID of the calendar event owner. For the External Calendar connection use `external_{salesloft_user_guid}` format. Example: `external_00210d1a-df8a-459f-af75-89b953b618b0`.
`payload.busy`	`boolean`	No	—	Should be set to `true` if the user is busy during the calendar event. Can be used in exchange with transparency param. Busy param has higher priority. Default: `true`.
`payload.attendees`	`object`	No	—	List of attendees of the calendar event. Example: `{ ... "attendees": [ { "name": "Alice", "email": "alice@example.com", "status": "accepted", "organizer": true }, { "name": "Bob", "email": "bob@example.com", "status": "needsAction", "organizer": false } ] }` `name`: full name of the attendee `email`: email address of the attendee `status`: one of the following - needsAction, accepted, tentative, declined `organizer`: whether the attendee is the organizer of the calendar event
`payload.all_day`	`boolean`	No	—	Should be set to `true` for all day calendar events.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.meeting_link`	`string`	No	—	The meeting join URL (e.g. Google Meet or Microsoft Teams link), if available.
`result.data.is_performed_by_organizer`	`boolean`	No	—	Whether the action on this calendar event was performed by the organizer of the event. False when a non-organizer attendee removes the event from their calendar (e.g. ‘this and following’ decline).
`result.data.organizer`	`string`	No	—	The organizer email of the calendar event.
`result.data.end_time`	`string`	No	—	The (exclusive) end time of the calendar event. Format: `date-time`.
`result.data.attendees`	`array`	No	—	The attendees of the calendar event.
`result.data.all_day`	`boolean`	No	—	Whether the calendar event is an all-day event.
`result.data.busy`	`boolean`	No	—	Busy/free status of the calendar event
`result.data.body_html`	`string`	No	—	Raw body content from Microsoft calendar events
`result.data.recurring`	`boolean`	No	—	Whether the calendar event is a recurring event.
`result.data.series_master_event_id`	`string`	No	—	INTERNAL: The ID of the recurring event series master event. This field is omitted for single events or instances of recurring events.
`result.data.created_at`	`string`	No	—	Creation time of the calendar event. Format: `date-time`.
`result.data.location`	`string`	No	—	Location of the calendar event
`result.data.status`	`string`	No	—	The status of the calendar event. It can be empty for non-google events.
`result.data.start_time`	`string`	No	—	The (inclusive) start time of the calendar event. Format: `date-time`.
`result.data.previous_values`	`record`	No	—	Previous values of the calendar event fields before the last update.
`result.data.updated_at`	`string`	No	—	Last modification time of the calendar event. Format: `date-time`.
`result.data.conference_data`	`record`	No	—	The conference-related information, such as details of a Google Meet conference.
`result.data.canceled_at`	`string`	No	—	The canceled date of the calendar event. Format: `date-time`.
`result.data.creator`	`string`	No	—	The creator email of the calendar event.
`result.data.tenant_id`	`integer`	No	—	Tenant ID of the user calendar
`result.data.recurring_interval`	`string`	No	—	Specifies how often a recurring event repeats (Daily, Weekly, Monthly, Yearly). This field is omitted for single events or instances of recurring events.
`result.data.out_of_office_properties`	`record`	No	—	Out-of-office properties for Google Calendar out-of-office events. Contains decline message and auto decline mode.
`result.data.html_link`	`string`	No	—	An absolute link to this calendar event in the Google Calendar Web UI.
`result.data.recurrence`	`array`	No	—	List of RRULE for a recurring event, as specified in RFC5545. This field is omitted for single events or instances of recurring events.
`result.data.description`	`string`	No	—	Description of the calendar event
`result.data.calendar_id`	`string`	No	—	Calendar ID of the user calendar.
`result.data.provider`	`string`	No	—	The provider of the calendar event.
`result.data.id`	`string`	No	—	The calendar event original ID from calendar provider
`result.data.extended_properties`	`record`	No	—	Extended properties of the calendar event.
`result.data.i_cal_uid`	`string`	No	—	Calendar event unique identifier (iCalUID)
`result.data.user_guid`	`string`	No	—	User GUID of the user calendar.
`result.data.title`	`string`	No	—	Title of the calendar event
`result.data.last_occurrence_at`	`string`	No	—	The timestamp of the last occurrence in a series of recurring events. Format: `date-time`.
`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.

Getting Started

GTM is code

Features

Deepline SDK beta

Integrations

API Reference

Salesloft: Calendar Events Upsert Create

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation