Skip to content

creatop-gtm/apollo-operator / plugins/apollo-operator/skills/operator-context

operator-context

Verified

Operator context for running B2B outbound on Apollo.io through the Apollo MCP. Load this first. Provides the Apollo tool map, universal deliverability and copy rules, the shared profile.yaml object, and routing to every other Apollo Operator skill. Use for any outbound task on Apollo: targeting, list building, sequences, deliverability, sending, or iteration.

FileKindSize
SKILL.mdskill md24.9 KB
connector-only.mdmarkdown19.3 KB
references/apollo-kb-map.mdmarkdown4.9 KB
references/compliance.mdmarkdown5.5 KB
references/operator-voice.mdmarkdown12.8 KB
references/outbound-principles.mdmarkdown6.1 KB
references/runtime.mdmarkdown7.0 KB

references/compliance.md

View on GitHub
# Compliance: operating rules for outbound on Apollo

> **Not legal advice.** Outreach law differs by country, changes, and depends on your business. These are the operating habits this library runs on so that opt-outs, privacy settings, and call registries are handled by default rather than remembered. Agree the legal basis for your own motion with whoever owns legal for the business.

Where this reference cites Apollo's own behaviour, the source is Apollo's help center (article names given) or a live check on a real account, dated.

---

## 1. Every cold email carries an opt-out, and every opt-out is honoured

- **Sequence emails:** Apollo attaches an unsubscribe link to emails sent from sequences, and a recipient who unsubscribes is removed from future steps in every sequence they are in (Apollo help center, "Configure Your Email Unsubscribe Link"). **Check the setting is on in the workspace before the first send.** No API field exposing it was found on 2026-09-14, so this is a UI check.
- **One-off emails** (sent outside a sequence): do not assume the link is attached. Write an opt-out line into the email yourself.
- **A real physical address** belongs in every cold email, usually in the signature.
- **A plain-language opt-out line helps, and does not replace the link.** "Reply 'no thanks' and I'll close the loop" is good copy; it only works if someone actually reads and actions the reply.

## 2. Opt-outs outlive the tool

Apollo's own unsubscribe handling protects Apollo sequences. It does not follow a person into a rebuilt list, a re-enrichment, or another sending platform. So:

- **Add every unsubscribe, "not interested", and complaint to the suppression file** the moment it happens, and subtract that file from every new list before enriching (see `apollo-list-builder`, step 3).
- **Never re-engage them**, however much time passes (see `re-engagement`).

Where to read them, all verified 2026-09-14:

| Source | What it gives |
|---|---|
| `apollo_analytics_sync_report`, metric `num_emails_unsubscribed` | Unsubscribe counts by sequence, step, or period |
| `apollo_emailer_messages_search` in `metadata_mode` | The Unsubscribed count for one sequence |
| `apollo emails search --stats replied` (CLI) | Replies Apollo classed as `unsubscribe` |
| `opt_out_rate` on each sequence object | The sequence's opt-out rate |

## 3. EU contacts: decide before you prospect, not after

- **Apollo has a workspace-wide GDPR setting** that removes EU-located people from prospecting, emailing, and email tracking for every user (Apollo help center, "Configure GDPR Settings on Apollo", under Settings, Rules of engagement, Prospecting config).
- **Read its state before building a list.** Contact search responses carry `disable_eu_prospecting` (`false` on the account checked 2026-09-14). If it is off and your ICP includes EU countries, that is a decision someone should make on purpose.
- **If you do prospect EU people:** have a documented lawful basis agreed with whoever owns legal, keep the message relevant to the person's role, include the opt-out, and honour removal requests promptly. Apollo keeps a Removal Requests list for requests it receives.
- **Person-level website visitor identification is US only** in Apollo, so first-party intent angles rarely reach EU people anyway (see `apollo-signals`).

## 4. Calls: screen before anyone dials

- **Apollo's DNC screening** checks phone numbers against do-not-call registries in the US, Germany, France, Canada, Australia, and the UK (TPS and Corporate TPS). Flagged numbers show "Do Not Call" and are blocked from Apollo's dialer, including numbers imported from a CRM; a user can override per contact where they have consent (Apollo help center, "Enable Do Not Call (DNC) Phone Screening"). It has to be enabled.
- **Reading the status:** phone numbers returned by a reveal carry `dnc_status_cd`. Only `found` means the number is on a registry. `pending` means screening is still running, **not** that the number is clear. Saved contacts' phone numbers carry `dnc_country_supported`, which says whether the number's country can be screened at all.
- **Numbers dialed outside Apollo are not blocked.** If a call task is worked from a personal phone or another dialer, check the status first (see `apollo-multichannel`).
- Since 2026 Apollo also exposes DNC status in CRM field mapping and CSV exports, and a call restrictions filter in search, per its release notes.

## 5. Recorded calls need consent where the law requires it

Some jurisdictions require every party's consent to record a call. Apollo added recording-rule guardrails for two-party consent jurisdictions in 2026, per its release notes. If calls are recorded, follow those rules, and treat the recordings and transcripts as confidential source material (see `business-brief`).

## 6. Business contacts only

Do not email consumers. Cold outreach in this library targets people in their professional role at their business address. Contacts carry a `free_domain` flag; a free-mail address on a B2B list is a list problem to remove, not a person to email.

## 7. Prospect data stays private

Lists, enriched records, replies, and call recordings belong to the business running the motion. Never paste them into anything published or shared with a third party, and describe patterns rather than people when discussing results.

---

## What Apollo does not do for you

- Carry opt-outs into other tools or future lists. The suppression file does.
- Decide whether you have a lawful basis to contact someone.
- Block numbers dialed outside its own dialer.
- Show, through the API, whether the unsubscribe link setting is on.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall