Documentation

Start a sequence

The seven ways a person can enter a sequence, including from your own server.

The trigger at the top of a sequence decides who enters it and when. Click it and choose under Starts when.

TriggerA person enters when
An event happensThey do something your product reports, such as signing up
Enters a segmentThey start to match a segment
Leaves a segmentThey stop matching a segment
A date arrivesA date stored on them comes up, such as a renewal date
A repeating scheduleThe day comes round, for everyone in a segment
A webhook is calledAnother system calls an address FounderHQ gives you
Manual onlyYou enroll them yourself

An event happens

Enter the Event name, exactly as your product sends it. See Getting started for sending events.

Filter by event property narrows it: only purchase events where plan is pro. Every filter must match.

An event older than 7 days does not start a sequence.

Enters or leaves a segment

Pick the segment. You build segments in Sequences → Segments, from rules about a person's attributes, events, visits, devices, and consent.

A date arrives

SettingChoices
Date attributeThe date on the person to use
RepeatsExact date, or Every year for a birthday or an anniversary
WhenDays before, On the day, or Days after

Then set the time of day and the time zone.

A repeating schedule

Choose Who, a segment, and Every day, week, or month.

Set the sequence's Re-entry policy to something other than Never. Otherwise each person enters once and gets nothing on the later dates. FounderHQ stops you from publishing until you do.

A webhook is called

Use this to start a sequence from a tool that can call an address: a form builder, a CRM, an automation tool.

  1. Choose how to find the person under Match contacts by: Email, Phone, or External ID.
  2. Under Field in the payload, name the field of the request that holds it.
  3. Turn on Create unknown contacts to add people FounderHQ has not seen.
  4. Copy the request FounderHQ shows, and give its address to the other tool.

The address works once the sequence is published. Set an Auth secret so that only your tool can call it.

Manual only

Nobody enters by themselves. Press Enroll at the top of a published sequence, then choose a whole segment or pick people one by one.

People already in the sequence are skipped, not added twice.

From your own server

Your backend can enroll a person in any published sequence with one request. Use it when your code already knows the moment.

Create a secret key with Add people to sequences: see API keys.

Nothing is sent anywhere. A publishable key is saved in this browser. A secret key is kept only until you reload.

curl https://app.getfounderhq.com/api/enrollments \
  -H "Authorization: Bearer fhq_sk_XXXX" \
  -H "Content-Type: application/json" \
  -d '{
    "sequenceId": "SEQUENCE_ID",
    "contact": { "externalId": "user_8421", "email": "jane@acme.com" },
    "variables": { "plan": "pro" }
  }'
FieldWhat it is
sequenceIdThe sequence to enter. It is the last part of the builder's address.
contactWho to enroll: externalId, email, or phone. FounderHQ creates the contact if it is new.
contactIdsInstead of contact: up to 1,000 FounderHQ contact IDs
variablesValues for the sequence's variables

A successful request answers 201.

In a message, a variable reads {{ vars.plan }}.

Verify

After you publish, cause the trigger once with your own account. Open Sequences → Message log: the first message of the sequence is in the log.

AI agent or LLM? Read this page as markdown

On this page