Update Campaign

Updates an existing campaign in Let's Calendar.

PUT

Query

Field selectionChoose which fields should be included in the response. Learn more

string

Comma-separated response fields to include.

Body

Arguments

stringrequired

The unique identifier of the campaign to update.

stringrequired

The title of the campaign.

stringrequired

The email subject line.

stringrequired

Type of event: online, offline, or physical.

numberrequired

ID of the sender email to use.

stringrequired

Start date in Y-m-d format.

stringrequired

Start time in H:i format.

stringrequired

End date in Y-m-d format.

stringrequired

End time in H:i format.

stringrequired

Timezone for the event.

stringrequired

Description of the campaign.

stringrequired

HTML content for the invite email body.

string

Physical location for the event when the event type is physical.

string

Common login URL for offline events.

Try this request

Request

curl --request PUT \
  --url "https://connect.mindcloud.co/v1/universal/letsCalendar/0.0.7/actions/update-campaign" \
  --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{
  "connectionId": "$CONNECTION_ID",
  "campaignId": "",
  "title": "",
  "subject": "",
  "eventType": "",
  "startDate": "",
  "startTime": "",
  "endDate": "",
  "endTime": "",
  "timezone": "",
  "description": "",
  "emailContent": ""
}'

{
  "success": true,
  "data": [
    {
      "campaign": {
        "endDatetime": "string",
        "id": "string",
        "startDatetime": "string",
        "timezone": "string",
        "title": "string"
      },
      "message": "string"
    }
  ],
  "meta": {}
}

Every app you connect,one REST pattern

Call any app with one REST pattern. MindCloud handles each provider's auth, request shape, and responses for you.

Learn what the Universal API is

One REST patternUse the same request structure across apps like Slack, HubSpot, Salesforce, and thousands more.

Managed connectionsSend a MindCloud connection ID instead of handling provider tokens, refresh logic, and credential storage yourself.

Action-level docsEach action page shows the exact endpoint, required arguments, optional controls, and response behavior for that app version.