Core concepts

A quick reference for the building blocks you'll encounter everywhere in Aigeon.

Organizations

Every user belongs to one or more organizations, and every object (contact, template, flow) is scoped to exactly one. Inviting someone to your org grants them a role — admin can change settings and billing, user can design and send.

Contacts, lists, and segments

A contact is a single recipient record keyed by hashed email. Contacts carry properties (first name, tags, custom fields) that you can set via CSV import, the web console, or the API.

A list is a named manual collection of contacts — you put people in, you take people out.

A segment is a saved query. "Opened a welcome email in the last 30 days and lives in California" is a segment. Segments re-evaluate at send time so they stay fresh automatically.

Templates and content

A template is the email design. Templates use Aigeon's component system (headers, articles, dividers, polls, ads, buttons) and keep a version history. When a flow or campaign references a template, it captures the active version at send time — later edits don't retroactively change sent messages.

Flows and campaigns

A flow is an automation graph. Triggers (signup, custom event, segment entry) start people into the graph; action nodes (send email, wait, branch on condition) decide what happens next. Flows are the right tool for welcome series, drip courses, abandoned-cart reminders, or anything that happens again and again.

A campaign is a single broadcast. Pick recipients, pick a template, click send. One-off newsletters, product announcements, event reminders.

Sending domains

To get good inboxing, Aigeon sends from your domain, not a generic shared one. Authenticate the domain once (SPF, DKIM, DMARC) and every flow or campaign you ship from that domain inherits the reputation. You can have multiple authenticated domains per org and pick which one sends which email.

API keys, webhooks, and MCP

These three surfaces expose everything the web console can do to external code:

• API keys are Bearer-style tokens scoped to specific permissions. See API keys & permissions.
• Webhooks push events from Aigeon to your endpoint when something happens (open, click, bounce, unsubscribe). See Overview.
• MCP servers expose the same capabilities to AI agents via the Model Context Protocol. See Overview.