Use case · Your team · Pipeline

Send a brief, collect interested replies in a table

Apollo sends. Smartlead schedules. Neither closes the loop. Magnis sends, then arms triggers on each prospect's address — when a reply lands, it categorises the signal and appends to a live pipeline-table. Every reply you don't write is a decision someone else makes for you.

Try Magnis Skip to the trigger flow ↓

🧪

Demo workspace — the 5 prospect addresses below are simulated. Replies from Northstar and Clearwell are mock data. When you self-host, your real Gmail connector + triggers run on real outbound.

Step 1

Describe the task

One line covers four operations: discovery, drafting, trigger arming, table creation.

You ask

Find five healthcare ops prospects, send the pilot proposal, set triggers on replies, and collect results into a table.

Step 2

Trigger arming

Magnis arms one multi-watch triggeron all five prospect addresses (OR-matching) — not five separate triggers. When new prospects join the campaign, Magnis adds them to the existing trigger's watch list. No re-arming. No dropped events.

Trigger created

{
  "tool": "email.set_trigger",
  "from_addresses": [
    "nora@northstarclinics.example",
    "julia@clearwellhealth.example",
    "ops@harborloop.example",
    "contact@atlasspecialty.example",
    "hello@pineviewmedical.example"
  ],
  "gate_prompt": "Is this a reply to our pilot outreach? Look for interest, pricing, timeline, procurement keywords.",
  "action_prompt": "Extract company, contact, signal type, requested material, next action with confidence. Append to Healthcare Outreach Collection Table.",
  "debounce_seconds": 0
}

The gate prompt classifies the reply. The action prompt writes to the collection table. Everything happens in the background — no re-prompting.

Step 3

What Magnis creates

Live pipeline-table. Two replies have landed (Northstar + Clearwell). Three triggers are still armed, awaiting responses. Magnis updates the table when each reply arrives — without asking you to re-run anything.

Healthcare Outreach Collection Table

Last update — Mar 14, 2026 · 09:42 (auto-update from trigger)

Company	Signal	Next action	Conf
Northstar Clinics Nora Singh, COO	interested	Send case-studies pack	0.91
Clearwell Health Julia Reynolds, CEO	interested + asks pilot plan	Draft pilot scope + security one-pager	0.88
HarborLoop Care Ops team	—	Trigger armed — awaiting reply	—
Atlas Specialty Group —	—	Trigger armed — awaiting reply	—
Pineview Medical —	—	Trigger armed — awaiting reply	—

Three rows pending — Magnis will update them automatically when HarborLoop, Atlas, or Pineview reply. No follow-up prompt needed.

Step 4

Follow-up prompts

Reply now to the two who responded

“Send the case-studies pack to Northstar and the pilot scope to Clearwell. Hold for my approval.”

Add five more prospects

“Find five more healthcare ops prospects and add them to the existing trigger watch list.”

Escalate stale rows

“If a prospect doesn't reply within 7 days, draft a soft follow-up and surface it in the digest.”

Step 5

Tips & troubleshooting

One trigger, many addresses.

OR-matching across N addresses = one trigger entity. Edit the gate / action prompt once, applies to all. Don't create separate triggers per prospect.

Confidence threshold matters.

If the gate prompt returns confidence < 0.6, Magnis flags the row for human review instead of auto-categorising. Default threshold tunable per trigger.

Outbound drafts wait for approval.

In v1, every outbound email requires explicit approval before send. No autopilot mode. The trigger handles inbound only — outbound is always a human decision.

Run the loop on your own pipeline.

Connect your Gmail. Magnis arms triggers on your real outbound. Replies surface as table rows on your local graph.

Try Magnis Join the waitlist