{scope}
Send an email to thank them for their time and follow up. Use one of our templates based on the call outcome.
", "createdAt": "2024-06-26T18:37:01.146Z", "updatedAt": "2024-06-26T18:37:01.146Z" } }, { "id": "198771537", "stepOrder": 2, "delayMillis": 0, "actionType": "FINISH_ENROLLMENT", "createdAt": "2024-06-26T18:37:01.146Z", "updatedAt": "2024-06-26T18:37:01.146Z" } ], "settings": { "id": "18167737", "eligibleFollowUpDays": "BUSINESS_DAYS", "sellingStrategy": "LEAD_BASED", "sendWindowStartMinute": 480, "sendWindowEndMinute": 1080, "taskReminderMinute": 480, "individualTaskRemindersEnabled": false, "createdAt": "2024-06-26T18:37:01.146Z", "updatedAt": "2024-06-26T18:37:01.146Z" }, "dependencies": [ { "id": "15241774", "createdAt": "2024-06-26T18:37:01.146Z", "updatedAt": "2024-06-26T18:37:01.146Z", "dependencyType": "TASK_COMPLETION", "requiredBySequenceStepId": "198771536", "reliesOnSequenceStepId": "198771535", "requiredByStepOrder": 1, "reliesOnStepOrder": 0 }, { "id": "15241775", "createdAt": "2024-06-26T18:37:01.146Z", "updatedAt": "2024-06-26T18:37:01.146Z", "dependencyType": "TASK_COMPLETION", "requiredBySequenceStepId": "198771537", "reliesOnSequenceStepId": "198771536", "requiredByStepOrder": 2, "reliesOnStepOrder": 1 } ] } ``` The details of each response field are outlined in the table below: | Field | Type | Description | | ------- | ------ | ------------------------------------------------------------------------------------------------------------------------------- | | `id` | String | The sequence ID. | | `name` | String | The name of the sequence. | | `steps` | Array | The list of steps in your sequence. Each step is an object that includes details like the type, priority, and creation details. | ## List sequences To get details about a specific sequence in your account, make a `GET` request to `/automation/v4/sequences/?limit=#&userId={userId}`. Use the amount of sequences you want returned as the limit in the request URL and use your [userID](/api-reference/legacy/crm/objects/users/guide) as a query parameter. For example, to get a list of four sequences and your user ID is `2222222`, make a `GET` request to `/automation/v4/sequences?limit=4&userId=2222222`. The response for fetching a list of sequences would resemble the following: ```json expandable theme={null} { "total": 7, "results": [ { "id": "88180366", "name": "Melinda's call sequence", "createdAt": "2023-07-20T15:40:04.364Z", "updatedAt": "2023-07-20T15:40:04.364Z", "userId": "2222222" }, { "id": "76853632", "name": "Melinda's Follow-up Sequence", "createdAt": "2023-01-26T15:38:05.812Z", "updatedAt": "2023-01-27T16:06:12.562Z", "userId": "2222222" }, { "id": "76897322", "name": "Melinda's Marketing Pro Demo Sequence", "createdAt": "2023-01-27T16:42:29.487Z", "updatedAt": "2023-05-03T14:40:42.507Z", "userId": "2222222" }, { "id": "76849666", "folderId": "67555200", "name": "Melinda's Sales Sequence", "createdAt": "2023-01-26T15:26:56.574Z", "updatedAt": "2023-05-26T17:16:57.866Z", "userId": "2222222" } ], "paging": { "next": { "after": "NA%3D%3D", "link": "https://api.hubspot.com/automation/v4/sequences/?limit=4&userId=8698664&portalId=6331522&hs_static_app=api-goggles&hs_static_app_version=1.7830&after=NA%3D%3D" } } } ``` The details of each response field are outlined in the table below: | Field | Type | Description | | ----------- | ------ | ----------------------------------------------------- | | `total` | String | The number of sequences in your account. | | `id` | String | The sequence ID. | | `name` | String | The name of the sequence. | | `createdAt` | String | The time the sequence was created in UTC format. | | `updatedAt` | String | The time the sequence was last updated in UTC format. | | `userID` | String | The userID of the user who created the sequence. | ## Enroll a contact in a sequence To enroll a contact in a sequence, make a `POST` request to `/automation/v4/sequences/enrollments/`. Use your [user ID](/api-reference/legacy/crm/objects/users/guide) as the query parameter. Specify the sequenceId, contactId, and senderEmail in the body. The senderEmail must be an email address that's [connected](https://knowledge.hubspot.com/connected-email/connect-your-inbox-to-hubspot) to your HubSpot account. For example, to enroll a contact whose ID is `33333` in sequence that’s ID is `44444444`, you’d make a `POST` request to `/automation/v4/sequences/enrollments`. The body would resemble the following: ```json theme={null} { "sequenceId": "33333", "contactId": "44444444", "senderEmail": "menelson@hubspot.com" } ``` The response for enrolling a contact in a sequence would resemble the following: ```json theme={null} { "id": "2435404604", "toEmail": "RachelGreen.com", "enrolledAt": "2024-06-27T20:11:02.824Z", "updatedAt": "2024-06-27T20:11:02.824Z" } ``` The details of each response field are outlined in the table below: | Field | Type | Description | | ------------ | ------ | ----------------------------------------------------------------- | | `id` | String | The ID for the enrollment object. | | `toEmail` | String | The email of the contact | | `enrolledAt` | String | The time the contact was enrolled in the sequence in UTC format. | | `updatedAt` | String | The last time the enrollment was updated (paused, unpaused, etc.) |