42min

    Help Integrations

    Snov.io

    Connect Snov.io so the people who book with you — and anyone who fills in a routing form — land in your Snov.io prospect lists automatically, instead of being copied over by hand. You set it up on the Integrations page under CRM, and once it's connected there's a settings page and a sync log.

    Note

    Snov.io's public API is built for lead-gen and outreach, not full CRM writes. It only lets apps add and update prospects in lists. So 42min syncs your invitees and form respondents as prospects — it does not create deals, log activities, or write notes. Those stay inside Snov.io's own interface.

    What it does

    • Connect your Snov.io account with an API user ID and API secret (no OAuth — you paste the keys from your Snov.io account).
    • Add invitees as prospects — when a meeting is booked, the invitee is upserted into the Snov.io list you choose.
    • Add routing-form respondents — optionally push people who submit a routing form into the same list.
    • Pick what triggers a sync — new booking, cancellation, reschedule, no-show, and routing-form submission, each on its own toggle.
    • Map fields — decide which booking and form fields fill the prospect's name, phone, company, and any custom fields.
    • Track the meeting's status — optionally write "Meeting booked / canceled / rescheduled / No-show" into an existing Snov.io custom field as the booking changes.
    • Watch the sync log — recent syncs and any errors, on the integration's log page.

    When to use it

    • You run outreach or lead-gen in Snov.io and want booked meetings to appear there without manual entry.
    • You want form respondents collected as prospects for follow-up.
    • You want a lightweight record in Snov.io of who booked and what happened to the meeting (kept, canceled, rescheduled, no-show).

    If you need deals, activities, or richer CRM records synced, that's beyond what Snov.io's API allows — consider Pipedrive instead.

    How to connect

    Connecting is admin-only (organization owners and admins).

    1. In Snov.io, open Account settings → API and copy your API user ID and API secret.
    2. In 42min, open Integrations, find Snov.io under CRM, and click Connect Snov.io.
    3. Paste the API user ID and secret and confirm. 42min checks the keys against Snov.io before saving — if they're rejected, double-check you copied both values.
    4. Once connected, open Settings to choose the target list and what syncs.

    Choose the list and what syncs

    Open the Snov.io settings page to configure the sync.

    Target list. Pick the Snov.io list your prospects go into. You can also create a new list right from this page. A target list is required — until you pick one, nothing syncs (the sync log records a clear "no target list" skip).

    Warning

    Adding a prospect to a list that has an active Snov.io campaign can automatically start that campaign's outreach to the person. Choose the target list carefully — point it at a plain list if you don't want booking to trigger emails.

    Triggers. Turn each event on or off:

    • Booking created — on by default.
    • Booking canceled — on by default.
    • Booking rescheduled — on by default.
    • Booking no-show — on by default.
    • Routing form submitted — off by default; turn it on to sync form respondents.

    If the prospect already exists. Choose Update (default — refresh the existing prospect with the new details) or Skip (leave an existing prospect untouched). Status updates from a later cancel, reschedule, or no-show always update the prospect regardless of this setting.

    Track the meeting status

    Snov.io's API has no notion of a meeting "stage," so 42min writes the status into an existing Snov.io custom field of your choice.

    1. On the settings page, under Lifecycle status field, pick an existing Snov.io custom field.
    2. Adjust the wording for each state if you like — the defaults are Meeting booked, Meeting canceled, Meeting rescheduled, and No-show.

    If you don't pick a custom field, cancellations, reschedules, and no-shows are skipped (there's nothing 42min can write for them) — only the initial "created" sync runs. You can also pick a Host email field to record which 42min host the meeting was with, for attribution.

    Map fields

    Email, name, and phone are mapped for you and can't be removed (the lock icon). Add your own rows to send more:

    • Source — invitee_form_question:<id> for a booking-form answer, or routing_form_field:<id> for a routing-form answer.
    • Target — a standard prospect field (prospect.company, prospect.companySite, prospect.position, prospect.country, prospect.locality, …) or a Snov.io custom field written as prospect.cf_<customFieldKey>.

    Blank rows are dropped when you save, so a saved mapping always does something.

    Common pitfalls

    • No email, no prospect. Snov.io requires an email on every prospect. A booking or form submission with no email address is skipped — you'll see it in the sync log.
    • Connected but nothing appears. Make sure you've chosen a target list and that the relevant trigger is on. With no list selected, every sync is skipped.
    • Routing-form respondents missing. "Routing form submitted" is off by default — turn it on if you want them.
    • Cancel/reschedule/no-show not reflected. Those only update Snov.io if you've chosen a Lifecycle status field; without one they're skipped.
    • Outreach fired unexpectedly. That's the active-campaign behavior above — the target list had a running campaign.
    • Sync errors. The sync log surfaces them (rejected credentials, a deleted list, rate limits). Snov.io limits API calls, so large bursts of bookings sync a little behind rather than all at once. Fix the cause and the job retries.
    • Disconnecting. Removing the connection stops future syncs; prospects already added to Snov.io are not deleted.

    Last updated June 3, 2026.

    PreviousPipedriveNext Calendly import