---
title: "List automations"
method: GET
path: "/api/reach/v1/profiles/{profileUuid}/automations"
tags: ["Reach: Automations"]
---

# List automations

`GET /api/reach/v1/profiles/{profileUuid}/automations`

Get a paginated list of the automations in a profile.

Every automation comes with the counts of contacts that entered it, are moving through it,
finished it or failed on the way. Those counts describe the contact journey and are not
email engagement metrics - for opens, clicks and unsubscribes use the campaign statistics
endpoint instead.

## Path parameters

- `profileUuid` string, required

## Query parameters

- `status` 'active' | 'paused' | 'draft'
- `sort_direction` 'asc' | 'desc'
- `page` integer
- `per_page` integer

## Response `200`

Success response

- object
  - `data` ReachV1AutomationsAutomationResource[] — Array of [`Reach.V1.Automations.AutomationResource`](#model/reachv1automationsautomationresource)
    - `uuid` string
    - `name` string
    - `status` 'active' | 'paused' | 'draft' — There is no `completed` status. Use `events.completed` to see how many contacts finished.
    - `type` 'welcome' | 'welcome_series' | 'promotional_series' | 'trust_building_series' | 'ecommerce_abandoned_cart' | 'ecommerce_recommend_after_purchase' | 'ecommerce_post_purchase' | 'ecommerce_discount_after_purchase' | 're_engagement_non_openers' | 're_engagement_non_clickers' | 'form_submitted' | 'custom' — What kind of workflow this is. `custom` automations are the ones built from scratch.
    - `config` object, nullable — Trigger configuration of the automation. The shape depends on the type.
    - `events` ReachV1AutomationsAutomationEventsResource — Counts of contacts moving through the automation. These are not email engagement metrics. Automations expose no sent, open or click counters - use the campaign statistics endpoint for those.
      - `started` integer — Contacts that ever entered the automation, including those that already left it.
      - `in_progress` integer — Contacts currently moving through the automation, including those waiting on a delay step.
      - `completed` integer — Contacts that reached the end of the workflow.
      - `failed` integer — Contacts whose journey through the automation errored and stopped.
    - `created_at` string, date-time, nullable
    - `updated_at` string, date-time, nullable
  - `meta` CommonSchemaPaginationMetaSchema
    - `current_page` integer
    - `per_page` integer
    - `total` integer

## Other responses

- `401` — Unauthenticated response
- `500` — Error response

---

[API](https://skmtc.net/hostinger/apis/hostinger-api.md) · [All operations](https://skmtc.net/hostinger/apis/hostinger-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/hostinger/hostinger-api/revisions/0692bdc8e675/schema)