Skip to main content

MoltSets integration

CRM and support connector, available on Zeplik

MoltSets is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect MoltSets and Zeplik can act on your customer relationships and support for you: MoltSets provides people and company search, profile enrichment, email and mobile discovery, advertising identity resolution, and account usage data. You stay in the conversation while the assistant does the work in MoltSets directly.

Zeplik exposes 18 read actions and 2 write actions for MoltSets. Read actions run automatically; write actions stay off until you enable write access in Settings, so nothing is changed in MoltSets without your consent.

Try MoltSets on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

What Zeplik can do with MoltSets

Read from MoltSets (18)

Runs automatically in any conversation.

  • Find best email by linkedin

    Find the best validated email for one LinkedIn profile or a batch of up to 100, preferring business email and falling back to sensitive personal email. Each item counts against Enrichment Fair Use; found records consume tokens and misses do not. HTTP 200 may represent not_found or a partial batch, so retry only items omitted from a partial response.

  • Find best us personal email by linkedin

    Find the highest-confidence validated sensitive personal email for one US LinkedIn profile or a batch of up to 100. Use this instead of the standard US personal-email selector when provider-ranked highest-confidence selection is required. This billable endpoint is capability-gated: first call GET_ACCOUNT and require personal_email_available=true, otherwise MoltSets returns 403 plan_restricted. Each item counts against Enrichment Fair Use; found records consume tokens and misses do not. Non-US profiles return HTTP 200 not_found. HTTP 200 may also contain a partial batch, so retry only omitted items.

  • Find business email by linkedin

    Find a validated corporate email, without personal-email fallback, for one LinkedIn profile or a batch of up to 100. Each item counts against Enrichment Fair Use; found records consume tokens and misses do not. risk_score describes deliverability, not identity confidence. HTTP 200 may represent not_found or a partial batch, so retry only items omitted from a partial response.

  • Find business email by name

    Find a validated business email and matched LinkedIn URL from a person's name and company/domain. This is billed against Search Fair Use only when an email is found; every call still counts as a request. risk_score describes deliverability, not identity confidence, and a miss is HTTP 200 status=not_found.

  • Find business profile by name

    Find a sparse full person and company profile from a person's name and company or domain, optionally including experience. A matched result is billable against Search Fair Use and every call counts as a request. Results can contain sensitive personal contact data and identity hashes; personal-email or SHA-256 fields may be omitted by plan restrictions while the lookup still succeeds. A status of not_found is a successful lookup miss.

  • Find company by ip

    Resolve a B2B visitor IPv4 address to associated company domains and provider percentages. A found result is billable against Enrichment Fair Use; found records consume tokens, misses do not, and every call counts as a request. Consumer ISP addresses commonly return HTTP 200 status=not_found. Percentages are preserved as provider strings rather than interpreted as numeric confidence values.

  • Find email hashes by linkedin

    Retrieve sensitive ad-audience match keys for one LinkedIn profile URL or slug: at most one business and one personal email hash in both SHA256 and MD5 formats. This endpoint does not return multiple hashes or accept batches. It costs one token when data is found; an HTTP 200 not_found costs no tokens but still counts as one Enrichment Fair Use request. The endpoint is unavailable on the $397/month and $997/month plans, which return 403 plan_restricted; retrying or adding tokens does not remove that plan restriction.

  • Find linkedin by email

    Resolve one email address to the highest-confidence LinkedIn profile URL available from MoltSets. A found record consumes Enrichment Fair Use tokens; a miss consumes no tokens but every call counts as a request. A miss returns HTTP 200 with status=not_found. This lookup does not verify the email address.

  • Find linkedin profile

    Find matching person or company LinkedIn profiles from a person's name and company/domain. Set count_only=true for a non-fetching match count that consumes no records or tokens but still counts as a Search Fair Use request. Full results consume records and tokens only when found; not-found calls also count as requests. A miss is HTTP 200 status=not_found with an empty result list.

  • Find mobile advertising id by email

    Resolve one email address to at most one highly sensitive Mobile Advertising ID (MAID), such as an Android AAID or Apple IDFA, for advertising audience matching and cross-device targeting. This Enrichment lookup is billable when found; misses cost no tokens but still count against the Fair Use request limit. The endpoint is unavailable on the $397 and $997 monthly plans: those plans receive 403 plan_restricted, and retrying or adding tokens does not remove the restriction. A miss returns HTTP 200 with status=not_found and empty or null results. Handle the returned advertising identifier as highly sensitive identity data and use it only with appropriate authorization and privacy controls.

  • Find mobile phone by linkedin

    Find sensitive carrier-verified mobile data for one LinkedIn profile or a batch of up to 100. This requires a paid base plan and a separately billed phone-token subscription; first use GET_ACCOUNT to check phone_token_balance, phone_token_allowance, and phone_plan. Each returned number costs one phone token, while misses cost no phone token; insufficient balance can return 402 or an HTTP 200 partial batch, so retain completed results and retry only dropped items. Results are mobiles only, not landlines or VoIP, but they are not screened against Do Not Call registries. last_validated_at means active and in service on that date, not consent or permission to contact; the caller remains responsible for applicable calling, messaging, privacy, and DNC compliance.

  • Find personal email hash by business email

    Convert one business email into one sensitive SHA-256-hashed personal-email match key for customer-match and paid-advertising audiences. Hashing does not make this identity data non-sensitive. The endpoint does not accept aliases or batches and never returns multiple hashes. A found result consumes Enrichment tokens; a miss costs no tokens but still counts against the Fair Use request limit and returns HTTP 200 with status=not_found. This endpoint is unavailable on the $397/month and $997/month plans: those plans receive 403 plan_restricted, which retrying or adding tokens does not clear.

and 6 more.

Act in MoltSets (2)

Runs only after you enable write access.

  • Enrich linkedin profile

    Resolve a LinkedIn profile URL into a sparse full person and company profile, optionally including experience. A found result is billable against Enrichment Fair Use; found records consume tokens, misses do not, and every call counts as a request. Results can contain sensitive personal contact data and identity hashes; personal-email or SHA-256 fields may be omitted by plan restrictions while the lookup still succeeds. A status of not_found is a successful lookup miss.

  • Reverse lookup email

    Resolve one email or a batch of up to 100 into a sensitive sparse person and business profile, including company firmographics, LinkedIn URLs, confirmed work email, and personal emails on file. Each address counts against Enrichment Fair Use; found records consume tokens and misses do not. HTTP 200 can represent not_found or a partial batch, so retry only omitted items.

How to connect MoltSets

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try MoltSets immediately.

  2. Connect MoltSets

    Open Settings and go to Connectors, then press Connect on MoltSets. You can also connect from the MoltSets page in the app.

  3. Add your MoltSets API key

    Paste your MoltSets API key when prompted. Zeplik stores it securely on the server and starts working with MoltSets right away.

Frequently asked questions

Can I use MoltSets with Zeplik?
Yes. MoltSets is available as an integration on Zeplik. Connect it once and the AI assistant can work with your MoltSets account inside any conversation.
What can Zeplik do with MoltSets?
Once connected, Zeplik has 18 read and 2 write actions for MoltSets. MoltSets provides people and company search, profile enrichment, email and mobile discovery, advertising identity resolution, and account usage data.
How do I connect MoltSets to Zeplik?
You connect MoltSets by pasting your own MoltSets API key in Settings under Connectors. There is no separate app to install.
Does Zeplik change things in MoltSets without asking?
No. Zeplik reads from MoltSets by default. Any action that changes data in MoltSets requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting MoltSets cost?
Connecting MoltSets is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related crm and support integrations

More on Zeplik

Connect MoltSets to your AI assistant

Every model, one chat. Bring MoltSets into Zeplik and let the assistant do the work.