Aller au contenu
NouveauDécouvrir comment
Amélioration

Find non-email connectors in the connector browser

The connector browser's main view now shows non-email connectors like calendar and Telegram, and search there returns them instead of an empty state.

Publié
Lecture
2 min de lecture

Your connector browser now shows more than email providers. The default view surfaces the non-email connectors you can add — such as calendar and Telegram — and searching from that view finally returns them too.

What changed

The browser's default "All" view used to behave as if email were the only kind of connector. Non-email options like calendar and Telegram existed, but the main browse view didn't put them in front of you, so they were easy to miss entirely.

Search made this worse. Typing a query in the "All" view had no real search path of its own, so it fell through to an email-only empty state — which meant a search for a perfectly available non-email provider came back as "No connectors found." The connector was there; the view just couldn't show it to you.

Now the "All" view lists available non-email connectors right alongside email providers, and search in that view returns matching non-email providers as well. Whether you scroll or search, if a connector is available to add, the main view will surface it.

How to use it

  1. Open the connector browser and stay on the default "All" view.
  2. Scroll the list to see non-email connectors — such as calendar and Telegram — listed together with your email providers.
  3. Or type what you're after in the search box. Matching non-email providers now appear instead of an empty "No connectors found" state.
  4. Select the connector you want and add it the same way you'd add an email provider.

Why it matters

The whole point of a connector browser is to find what you can plug in without already knowing it's there. When the main view and its search only spoke email, anything else was effectively hidden — you had to know the exact path to reach it, which defeats the purpose of browsing.

If you run outreach across more than just email, this matters more the more channels you use. A calendar connection helps prospects book time with you; a channel like Telegram opens a path beyond the inbox. Being able to find and add those from the same place you manage email keeps your whole setup in one view, instead of scattered across places you have to already know about.

Now discovery works the way you'd expect. Whether you scroll the main view or search by name, the non-email connectors show up next to email, so you can see your full set of options and add the one you need in a couple of clicks. Less guesswork, fewer dead-end searches, and a clearer picture of everything you can connect.

Toutes les nouveautés

Une prospection qui continue quand vous vous déconnectez.Leads, emails, relances et réponses, gérés.

Connectez des boîtes illimitées et laissez les agents IA trouver les leads, écrire chaque email et relancer. Ou envoyez vos propres modèles en mode manuel. À partir de $29/mois.

Démarrez votre essai à $1 Voir les tarifs

$1 pour 3 jours · Annulez quand vous voulez · Sans engagement

Installer avec l'IA

Votre agent de code installe la CLI et les skills FirstSales pour vous.

Prompt pour 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 ↗