Pular para o conteúdo
NovoVeja como
Melhoria

Fine-grained two-way sync controls for your connectors

When you connect an email account, you now control how FirstSales uses it: keep incoming-email sync on or off, choose how far back to pull history (7 days to 2 years), and set who on your team can see the synced emails. Everything is editable anytime, with a live sync progress banner.

Publicado
Leitura
3 min de leitura

Connecting an email account is a moment of trust. You're handing a tool access to your inbox. The least it can do is be clear and adjustable about what it does with that access. Connector sync settings now put that in your hands: what gets synced, how far back, and who can see it.

What changed

When you connect an email account, or open one you've already connected, you now get three controls:

  • Sync incoming email: a toggle to keep pulling in replies and incoming mail, or turn it off entirely.
  • How far back to sync: choose the historical window, from 7 days, 30 days, 90 days, 6 months, and 1 year up to 2 years.
  • Visibility: decide whether synced emails are shared with the workspace or private to you.

You set these the moment you connect an account, on a dedicated setup step, or you can skip and take the sensible defaults (sync on, 90 days, shared). Everything is editable later from the connector's detail drawer, so no choice is permanent. Widen the history window and FirstSales confirms before it re-scans further back. Change visibility and a note reminds you it applies to newly synced emails going forward.

While a connector is catching up on history, a sync banner shows real progress, how far back it's reached, and clears itself once it's caught up. If an account's login ever breaks, that same banner turns into a Reconnect account prompt so you know exactly what to fix. And a send-only connector, which never receives mail, simply says so instead of showing sync controls it doesn't need.

How to use it

  1. Go to Connectors.
  2. Connect an email account, or open one you've already connected.
  3. On the sync step, keep or turn off Sync incoming email.
  4. Choose how far back to pull history, anywhere from 7 days to 2 years.
  5. Set visibility: shared with the workspace, or private to you.
  6. Save, or skip to take the defaults.
  7. To change any of it later, open the connector's detail drawer and edit the Sync section. Widening the window will ask you to confirm a re-scan.

Why it matters

Defaults are convenient until they're wrong for you, and inbox sync is exactly the kind of thing where one size doesn't fit. A solo founder wants everything shared and two years of history for full context. Someone connecting a personal account on a shared workspace wants it private and shallow. Forcing everyone into the same behavior means someone is always uncomfortable. Making it a choice, clearly at connect time and changeable after, respects that the same feature means different things to different people.

The progress banner and the reconnect prompt matter for a plainer reason: sync that happens invisibly is sync you can't trust. When you can see how far back it's reached and get told the moment something needs your attention, the connection stops being a black box. This builds on the connector work behind finding non-email connectors and the SPF, DKIM, and DMARC authentication checks that keep your sending healthy.

Todas as novidades

Prospecção que continua quando você desconecta.Leads, emails, follow-ups e respostas, resolvidos.

Conecte caixas ilimitadas e deixe os agentes de IA encontrarem leads, escreverem cada email e fazerem follow-up. Ou envie seus próprios modelos no modo manual. A partir de $29/mês.

Comece seu teste de $1 Ver preços

$1 por 3 dias · Cancele quando quiser · Sem contrato

Instalar com IA

Seu agente de código configura a CLI e as skills do FirstSales para você.

Prompt para Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.
Developer docs ↗npm: @firstsales.io/cli ↗GitHub: firstsales-skills ↗