For the complete documentation index, see llms.txt. This page is also available as Markdown.

What a play is

Play, run, activation: the three words, and how a motion actually executes.

Three words, one chain:

Play → runs → activations.

  • A play is a named, proven motion, "Convert Anonymous Traffic," "Find More Like Your Best Customers", with what it does and what it needs. Plays live in the library; selecting one opens a chat where iHarness makes it yours: your audience, your channels, your goal. The play stays editable through that same chat: swap Instantly for a different sender, retarget it, tune it.

  • A run is one execution of the play. Scheduled plays run on their cadence; each run is ledgered.

  • An activation is what a run delivers into a destination: the audience pushed to LinkedIn, the sequence started in Instantly, the list synced to your CRM. One play can hold several activations, and each contact's activation history is tracked individually.

You run a play, it leaves behind activations, and when those activations need you, they raise a hand in Pulse.

Plays are how automation happens

Anything scheduled or recurring is a play; a one-time export is just an export. Buyer-facing automation lives here; internal alerts live in Pulse. That split keeps one place to look for "what is running against my audience."

Nothing activates itself

Creating a play never spends money on its own. Activation, committing budget, sends, and credits, always requires your explicit confirmation. After that, the play works within your guardrails, including the platform-wide rule that one contact is in at most one active cadence at a time.

And every play accounts for itself

A running play produces decisions, each with its spend and its expectation on record. Browse what exists in the Play library; set one up in Setting up a play.

Last updated