CampaignSubsequence

Duplicate a subsequence

Changed on

Duplicate a subsequence with the same trigger conditions

Requires one of the following scopes: subsequences:create, subsequences:all, all:create, all:all

post/api/v2/subsequences/{id}/duplicate

Request

  • Base URL
    https://api.instantly.ai
  • URL
    https://api.instantly.ai/api/v2/subsequences/{id}/duplicate
  • Auth
    HTTP bearer

Path parameters

idstring uuid required
Example:123e4567-e89b-12d3-a456-426614174000

The ID of the subsequence to duplicate.

Request body

parent_campaignstring uuid required

The ID of the campaign to duplicate the subsequence to.

namestring

The name of the duplicate subsequence. Defaults to the source subsequence name when omitted.

Example request

{
  "parent_campaign": "123e4567-e89b-12d3-a456-426614174000",
  "name": "My Duplicate Subsequence"
}

Response

The requested Campaign Subsequence

idstring uuid required

Unique identifier for the subsequence

timestamp_createdstring date-time required

Timestamp when the subsequence was created

parent_campaignstring uuid required

ID of the parent campaign

workspacestring uuid required

ID of the workspace this subsequence belongs to

status-99 | -1 | -2 | 0 | 1 | 2 | 3 | 4 required

Status of the subsequence

timestamp_leads_updatedstring date-time required

Timestamp when the leads were last updated

namestring required

Name of the subsequence

daily_limit_mode'inherit' | 'custom' | 'unlimited'

Daily limit mode for the subsequence. "inherit" uses the parent campaign limit, "custom" uses a subsequence-specific limit, "unlimited" bypasses the campaign-level daily limit.

daily_limitnumber nullable

Custom daily limit for the subsequence. Only used when daily_limit_mode is "custom".

ignore_account_daily_limitboolean

When enabled, the subsequence will send even when sending accounts have reached their daily limit.

Example response

{
  "id": "01a19e6f-50b9-7983-8ce9-ee4cf3defee9",
  "timestamp_created": "2026-11-02T22:44:17.721Z",
  "parent_campaign": "01a19e6f-50b9-7983-8ce9-ee4d15185b59",
  "workspace": "01a19e6f-50b9-7983-8ce9-ee4eaa765608",
  "timestamp_leads_updated": "2026-11-02T22:44:17.721Z",
  "name": "Follow-up sequence",
  "conditions": {
    "crm_status": [
      1
    ],
    "lead_activity": [
      4
    ],
    "reply_contains": "yes"
  },
  "subsequence_schedule": {
    "start_date": "2025-09-25",
    "end_date": "2025-09-25",
    "schedules": [
      {
        "name": "My Schedule",
        "timing": {
          "from": "09:00",
          "to": "17:00"
        },
        "days": {
          "0": true,
          "1": true,
          "2": true,
          "3": true,
          "4": true
        },
        "timezone": "Etc/GMT+12"
      }
    ]
  },
  "sequences": [
    {
      "steps": [
        {
          "type": "email",
          "delay": 2,
          "delay_unit": "days",
          "pre_delay": 2,
          "pre_delay_unit": "days",
          "variants": [
            {
              "subject": "Hello {{firstName}}",
              "body": "Hey {{firstName}},<br/><br/>I hope you are doing well.",
              "v_disabled": true
            }
          ]
        }
      ]
    }
  ],
  "auto_variant_select": {
    "trigger": "click_rate"
  },
  "daily_limit_mode": "inherit",
  "daily_limit": 50
}

Changes

    • breaking

      the response property became optional for the status

    • breaking

      the response property became optional for the status

    • info

      the request property became optional

    • info

      added the optional property to the response with the status

    • info

      added 'contains' constraint to the //// response property for the status

    • info

      removed the -1.00 enum value from the // response property for the response status

    • info

      removed the -2.00 enum value from the // response property for the response status

    • info

      removed the -3.00 enum value from the // response property for the response status

    • info

      removed the -4.00 enum value from the // response property for the response status

    • info

      removed the 0.00 enum value from the // response property for the response status

    • info

      removed the 1.00 enum value from the // response property for the response status

    • info

      removed the 2.00 enum value from the // response property for the response status

    • info

      removed the 3.00 enum value from the // response property for the response status

    • info

      removed the 4.00 enum value from the // response property for the response status