Capability: List my sequences

“List my sequences” is a platform capability that returns a concise, sortable inventory of every email sequence you have currently active within your account. Each entry includes the sequence name, unique identifier, status (running, paused, or completed), start date, and the number of contacts enrolled. The function is exposed through the user interface as a dedicated tab and is also available via a lightweight API endpoint that returns JSON‑formatted data.

The purpose of this feature is to give marketers, sales ops teams, and customer‑success managers an at‑a‑glance view of their outreach workload, enabling quick audits, troubleshooting, and capacity planning without having to open each sequence individually.

When to use it

You should invoke “List my sequences” in the following scenarios:

Situation	Why the list helps	Typical action taken
Morning workflow review	Confirms which campaigns are live before you begin drafting new content	Prioritize sequences that need performance checks or copy updates
Audience segmentation audit	Shows how many contacts are enrolled per sequence, highlighting over‑ or under‑utilized lists	Adjust list assignments or pause low‑engagement sequences
Compliance spot‑check	Provides start dates and statuses needed to verify adherence to regulations such as CAN‑SPAM (FTC.gov)	Identify any sequence lacking required opt‑out links or sending beyond allowed windows
Incident response	When a delivery issue arises, the list isolates the affected sequence(s) for rapid investigation	Pause the problematic sequence, examine logs, and resume after fixing
Capacity planning	Displays the total number of active sequences, helping you gauge whether you are approaching platform limits	Decide whether to archive completed sequences or request additional quota

In each case, the list supplies the factual baseline needed for informed decision‑making, reducing reliance on memory or scattered notes.

Where does it run

The operation executes entirely within our secure, multi‑tenant environment. When you trigger the request—whether by clicking the “Sequences” tab in the web console or calling the /v1/sequences/list endpoint—the platform’s orchestration layer routes the call to the sequence metadata service. This service resides on the same isolated virtual private cloud (VPC) that stores your contact data, ensuring that no information leaves the trusted boundary.

Because the query only reads metadata (names, IDs, timestamps, and enrollment counts) and never touches message bodies or personal data beyond what is already stored for sequencing, the latency is consistently low: internal benchmarks show a median response time of 120 ms for accounts with up to 5,000 active sequences.

If you prefer an on‑premises deployment, the same metadata service can be instantiated in your private cloud, adhering to the same API contract and security controls.

How it works

Under the hood

1. Authentication & authorization – The request is first validated against your OAuth 2.0 token. The platform checks that the token bears the sequences:read scope; if not, a 403 response is returned immediately.
2. Metadata retrieval – The sequence metadata service queries a distributed, strongly consistent datastore (built on an industry‑leading infrastructure) for all records where sequence documents that match the caller’s tenant ID. Each document contains:

• sequence_id (UUID)
• name (user‑defined label)
• status (enum: active, paused, completed, draft)
• created_at (ISO‑8601 timestamp)
• contact_count (integer)
• last_updated_at (ISO‑8601 timestamp)

1. Result shaping – The service projects the raw documents into a lightweight JSON array, adds a total field for pagination, and applies any requested sort order (e.g., by name ascending or contact_count descending).
2. Response delivery – The payload is gzipped, transmitted over TLS 1.3, and delivered to the client. The entire pipeline is instrumented with OpenTelemetry traces, allowing us to measure latency and error rates in real time.

User interface walkthrough

1. Navigate – From the main dashboard, select Sequences in the left‑hand navigation pane.
2. View the table – The screen presents a sortable table with the columns described above.
3. Filter – A filter bar lets you narrow results by status, date range, or a keyword search on the sequence name.
4. Bulk actions – Checking one or more rows enables bulk pause, resume, or archive operations, which invoke the same backend endpoints used for individual actions.
5. Export – Clicking Export CSV downloads the current view (respecting any active filters) as a UTF‑8 encoded file, useful for offline audits or import into BI tools.

Example output

A typical JSON response for a user with three active sequences might look like this (pretty‑printed for readability):

{
  "total": 3,
  "sequences": [
    {
      "sequence_id": "a1b2c3d4-e5f6-7890-g1h2-i3j4k5l6m7n8",
      "name": "Welcome Series – New Leads",
      "status": "active",
      "created_at": "2024-02-10T08:15:00Z",
      "contact_count": 1,245,
      "last_updated_at": "2024-09-20T14:03:12Z"
    },
    {
      "sequence_id": "b2c3d4e5-f6g7-8901-h2i3-j4k5l6m7n8o9",
      "name": "Product Onboarding – Trial Users",
      "status": "paused",
      "created_at": "2024-04-22T11:02:00Z",
      "contact_count": 782,
      "last_updated_at": "2024-09-18T09:45:05Z"
    },
    {
      "sequence_id": "c3d4e5f6-g7h8-9012-i3j4-k5l6m7n8o9p0",
      "name": "Re‑engagement – Inactive Subscribers",
      "status": "active",
      "created_at": "2024-01-05T06:30:00Z",
      "contact_count": 3,410,
      "last_updated_at": "2024-09-21T16:22:38Z"
    }
  ]
}

The same data appears in the UI table, with the ability to click any row to open the sequence’s detailed editor.

FAQ

Q: Does “List my sequences” include draft or archived sequences? A: By default, the endpoint returns only sequences with a status of active, paused, or completed. Drafts and archived items are excluded to keep the view focused on operational workflows. If you need to see drafts, add the include_drafts=true query parameter; for archived items, use include_archived=true.

Q: How often is the contact count updated? A: The contact_count field is refreshed near‑real‑time as contacts enter or leave a sequence. Internally, the sequence engine increments or decrements a counter each time a subscription event is processed, and the metadata service reads this counter on each list request. Under heavy load, the count may lag by a few seconds, but it is always eventually consistent.

Q: Can I sort by the date a sequence was last modified? A: Yes. The API accepts a sort_by parameter with values created_at, last_updated_at, name, or contact_count. The UI provides a column‑header click to toggle ascending/descending order for each field.

Q: Is there a limit to how many sequences the list can return? A: The platform caps the response at 1,000 items per call to prevent excessively large payloads. If you have more than 1,000 sequences, use pagination (page and page_size parameters) or request a CSV export, which streams the full set without the per‑page limit.

Q: Are there any privacy or compliance concerns when exporting the list? A: The exported CSV contains only sequence metadata—no personal data, email addresses, or message content. Therefore, exporting the list does not trigger additional data‑processing obligations under GDPR, CCPA, or similar regulations. However, you should still treat the file as internal business information and apply your organization’s standard data‑handling policies.

Q: What happens if I accidentally pause a sequence that is currently sending? A: Pausing a sequence halts the scheduling of new messages but allows any in‑flight deliveries to complete. This design prevents abrupt termination that could leave contacts in an inconsistent state (e.g., receiving a partial follow‑up). You can resume the sequence at any time, and the scheduler will pick up where it left off.

Q: Does the list show A/B test variants? A: Each A/B test is represented as a separate sequence entry, with the parent test’s name appended by _variant_a or _variant_b. This makes it easy to compare performance across variants directly from the list view.

Q: Are there any costs associated with calling this endpoint? A: The operation is priced as part of your platform subscription. Costs are dynamically calculated based on the overall complexity of your account (number of sequences, frequency of metadata changes, and data transfer volume). There is no per‑call token or usage charge; instead, the platform allocates a quota of read operations that renews monthly.

Takeaway

“List my sequences” delivers a transparent, low‑latency snapshot of every‑sequence metadata that powers your day‑to‑day: quick audit compliance, capacity planning. By combining strong security, and real‑time design, it gives you confidence to manage your outreach at scale, guesswork.