Skip to content

Integration · CRM and sales

ApexVerify in Skyller.

Connect ApexVerify to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Actions and events

ApexVerify

ApexVerify validates and normalizes email addresses and phone numbers individually or in batches to improve contact-data quality.

Actions
10
Events
0
Composio catalog
API key
Global — no specific country
re-read from the vendor every 24 hours
www.apexverify.com

10 ACTIONS

published by the vendor; the company enables only the necessary ones

0 EVENTS

triggers the system can send, when the vendor offers them

API KEY

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, one query in ApexVerify and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in ApexVerify.

  1. Input

    A team member asks, in the conversation, for something that today requires opening ApexVerify — inside their area's space, with their login.

  2. What Skyller does

    1. 01Picks, among the enabled functions, a query action and looks the information up in ApexVerify with the person's own credential.
    2. 02If the request requires writing something in ApexVerify, shows the card with what it is about to do and waits for Approve.
    3. 03Returns the result in the conversation and records who asked, which action was used and when.
  3. Result

    ApexVerify stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

  • The available actions are the ones the vendor publishes for ApexVerify; in your company only the functions turned on by the administrator are available.
  • If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
  • Being in this catalog does not mean being installed, with a valid login, working in your company.

Where this helps your work

ApexVerify inside the conversation where the work happens.

Three common situations for people who use ApexVerify every day. What Skyller does in each one depends on the functions your company turns on.

Preparing the meeting

“Summarize this customer's history before the call.”

The salesperson asks by name. Skyller queries ApexVerify through the read functions enabled for sales and builds the summary with the latest interactions and the deal stage.

CRM context in the conversation

Logging the follow-up

“Create the follow-up activity for Friday.”

Creating a record in ApexVerify is a write action: Skyller shows the card with the deal, the date and the note and waits for Approve.

Record with approval

Administering

“Reading, yes. Changing a proposal's value, no.”

The administrator turns on reading and activity creation for the team; changing values and deleting records stay off. Every call to ApexVerify goes in the record.

Function by function

Actions and events

What the vendor offers in ApexVerify.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

  • Delete Batch

    APEXVERIFY_DELETE_BATCH

    Permanently delete one ApexVerify batch by its exact UUID. Deletion is irreversible and unavailable while the batch is processing; verify the target batch first and deliberately set confirm_deletion=true.

  • Export Batch Results

    APEXVERIFY_EXPORT_BATCH_RESULTS

    Export a completed batch as structured JSON for analysis or as a downloadable XLSX workbook. This reads existing results and does not consume verification credits.

  • Get Account Credits

    APEXVERIFY_GET_ACCOUNT_CREDITS

    Return the connected ApexVerify account's available email and phone verification credit balances. Use this before any credit-consuming verification.

  • Get Batch Details

    APEXVERIFY_GET_BATCH_DETAILS

    Get an ApexVerify batch's status, metadata, parsed-content counts, estimated verification cost, parameters, and final statistics. Repeat this call to monitor preparation or verification.

  • Launch Batch Verification

    APEXVERIFY_LAUNCH_BATCH_VERIFICATION

    Launch paid verification for a prepared batch. This consumes the batch's estimated net email or phone credits and can fail when credits are insufficient.

  • List Batches

    APEXVERIFY_LIST_BATCHES

    List verification batches, optionally restricted by creation time, one offset-controlled page at a time.

  • Normalize Data File

    APEXVERIFY_NORMALIZE_EMAIL_OR_PHONE_FILE

    Normalize email addresses or phone numbers from a line-delimited TXT file without performing verification or consuming verification credits.

  • Prepare Batch

    APEXVERIFY_PREPARE_BATCH

    Start or repeat asynchronous parsing, deduplication, format cleanup, and verification-cost calculation for an uploaded batch. This idempotent action does not launch paid verification.

  • Upload Verification Batch

    APEXVERIFY_UPLOAD_BATCH

    Create an ApexVerify verification batch from a line-delimited TXT file. Uploading does not consume verification credits; verification starts only when the batch is launched separately.

  • Verify Email or Phone

    APEXVERIFY_VERIFY_EMAIL_OR_PHONE

    Verify one email address or phone number in real time. This consumes the corresponding prepaid verification credit; cache hits may receive a partial refund.

Before you start

What your company needs to use ApexVerify.

Login
Each person enters their own ApexVerify API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs
An administrator connects ApexVerify for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions
10 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan
Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide

Common doubts before connecting ApexVerify.

Next step

Connect ApexVerify and try it with your team.

Try it free with your team or book a demo: together we pick the ApexVerify functions to enable and show the first approved action, with fictitious data.