Account Integrations
The Integrations page on the unified Aimly dashboard (aimly.online/dashboard/?tab=integrations, also reachable via Account → Integrations inside Aimly Email) manages third-party API keys and deliverability controls across Aimly Email, Finder, and AI Interface.
How API keys are stored and protected
Aimly uses a browser-bound key architecture for third-party provider credentials:
- Encrypted browser cookies — your AI, Web Search, and ZeroBounce API keys are encrypted with AES-256-GCM and stored in
HttpOnlybrowser cookies scoped to.aimly.onlinewith a 30-day lifetime from when each key was last saved. - No permanent database storage — third-party API keys are never persisted at rest in Aimly's primary account database. When you launch an asynchronous Finder search, active provider keys are encrypted transiently for that job and scrubbed automatically as soon as the search completes, stops, or fails.
- Per-browser scope — if you switch browsers, clear cookies, or use a new device, re-enter your provider keys under Integrations. External MCP Server clients and internal MCP tool calls do not receive browser cookies (see AI Interface).
Artificial Intelligence
Configuring an AI provider powers personalized email generation, sequence drafting, prompt optimization, Finder lead extraction, and the conversational AI Interface.
Supported AI providers and models
| Provider | Built-in models | Notes |
|---|---|---|
| Gemini | gemini-3-flash-preview, gemini-3.1-pro-preview, gemini-3.1-flash-lite | Fast, cost-effective structured extraction and outreach drafting. |
| Claude | claude-sonnet-4-5, claude-haiku-4-5 | Strong long-context reasoning and nuanced copywriting. |
| OpenAI | gpt-5.6-terra, gpt-5.1, gpt-4.1-mini | High-throughput tool calling and email personalization. |
| xAI | grok-4-fast | Low-latency chat and structured generation. |
| Custom | User-specified Model ID | Supports any OpenAI-compatible or Anthropic-compatible Base URL + Model ID. |
Finder model compatibility
When saving an AI key, Aimly validates whether the selected model meets Finder requirements:
- Must support structured tool/function calling.
- Must sustain at least 25,000 tokens per minute (TPM) so multi-company web extraction batches do not stall on rate limits.
Models that do not meet Finder's throughput or tool-calling requirements can still write emails if supported, while the UI displays a compatibility indicator for Finder.
Web Search providers
Web Search integrations power company discovery and contact enrichment in Finder. At least one enabled provider is required to run a Finder search.
| Provider | Role & requirements |
|---|---|
| Apify | Web scraping and business directory discovery. Requires at least $0.10 available account credit on connection. |
| Firecrawl | Deep website crawling and team/contact page extraction. |
| Tavily | AI-oriented live web search for company discovery and context research (company_info). |
| BetterContact | Waterfall B2B email and contact discovery with independent Lead Finder and Contact Enrichment sub-toggles. |
Enabling and ordering search providers
- On / Off toggles — temporarily disable any connected provider without deleting its saved key.
- Search order — drag or reorder providers using the priority controls. Finder queries enabled providers from left to right and falls back automatically to the next enabled provider if an upstream source exhausts its quota mid-search.
Email Health & Verification Strictness
The Email Health section controls which email addresses are permitted to enter Leads or receive campaign mail, alongside optional ZeroBounce verification.
Verification Strictness levels
| Strictness | Allowed statuses | Blocked statuses |
|---|---|---|
| High (default) | valid (plus unverified syntactic/MX-passing leads when ZeroBounce is not connected) | catch_all, unknown, plus all permanent block conditions below |
| Medium | valid, catch_all | unknown, plus all permanent block conditions below |
| Low | valid, catch_all, unknown | Only permanent block conditions below |
Regardless of strictness level, Aimly always blocks addresses marked invalid, spamtrap, abuse, do_not_mail, disposable_domain, no_mx, invalid_format, or hard_bounce.
Raising Verification Strictness (for example, from Low or Medium to High) immediately blocks existing leads whose verification status no longer qualifies — automatically cancelling their queued or scheduled emails and marking any active or paused automation executions for those leads as completed.
ZeroBounce integration
Connect a ZeroBounce API key to verify lead deliverability against live mail-server signals during CSV uploads, manual entry, and Finder runs:
- Live status verification — classifies addresses as
valid,catch_all,unknown,invalid,spamtrap,abuse, ordo_not_mail. - AI Email Quality Scoring (
0–10) — toggle on to score mailbox activity and quality from0.0to10.0automatically or via the inline Get score button in Leads and Finder.