Skip to main content

urlscan.io integration

Business connector, available on Zeplik

urlscan.io is available as an integration on Zeplik, the AI assistant that works across every model in one chat. Connect urlscan.io and Zeplik can act on your business operations for you: Submit and retrieve website scans, search urlscan.io data, and manage urlscan Pro resources for threat intelligence and security investigations. You stay in the conversation while the assistant does the work in urlscan.io directly.

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

Try urlscan.io 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 urlscan.io

Read from urlscan.io (29)

Runs automatically in any conversation.

  • Download file

    Retrieve a captured binary file by its SHA-256 hash as a password-encrypted ZIP archive. This operation requires urlscan Pro access.

  • Get account capabilities

    Get non-sensitive plan, product, feature, visibility, submission, and limit information for the connected urlscan.io API key.

  • Get brand summary

    Return detectable brands with detected-page totals and latest hits. This operation requires urlscan Pro access and uses the official contract only; the provider does not document its response fields.

  • Get channel

    Get one urlscan Pro notification channel by ID while preserving provider-specific metadata and removing webhook destinations or credentials.

  • Get data dump link

    Generate a temporary download URL for a path returned by LIST_DATA_DUMPS. Data Dumps require an Enterprise or Ultimate urlscan.io plan.

  • Get dom

    Return the plain-text DOM snapshot captured for a completed scan.

  • Get hostname history

    Return one page of historical Pro Hostnames observations for a hostname.

  • Get incident

    Get one incident's configuration, source, runtime state, and timestamps.

  • Get incident states

    Retrieve the stored state history for an incident.

  • Get live scan resource

    Retrieve one temporary result, DOM, screenshot, captured response, or download from the separate urlscan.io Live Scanning product. JSON and text are returned inline; binary content is offloaded as a downloadable file.

  • Get phishfeed

    Retrieve the deprecated urlscan Pro phishing feed in JSON, CSV, or TSV. Prefer SEARCH_SCANS for new workflows, as recommended by urlscan.io.

  • Get quotas

    Get current products, features, query capabilities, and per-action minute, hour, and day quota usage.

and 17 more.

Act in urlscan.io (22)

Runs only after you enable write access.

  • Close incident

    Stop ongoing scans for an active urlscan Pro incident and transition it to the closed state. Closing does not delete the incident or its history, and the incident can later be restarted.

  • Copy incident

    Create a separate urlscan Pro incident from an existing incident's configuration. This create operation can consume incident capacity and does not copy the source incident's stored state history; use the distinct fork operation when history must be preserved. The provider does not document whether the copied incident immediately activates ongoing scans or alerts.

  • Create channel

    Create a Pro notification channel. This operation configures external effects: active webhook channels send requests to the supplied secret URL, and active email channels send messages to the supplied recipients. Confirm the destination and activation settings before calling.

  • Create incident

    Create a Pro incident that persistently monitors an observable. This high-impact operation starts ongoing external scans and can send alerts through every supplied notification channel; confirm the observable, visibility, channels, cadence, and expiration settings before calling. The operation is contract-only because the connected build account lacks the urlscan Pro Incidents entitlement.

  • Create live scan blocking

    Run a temporary Live Scan synchronously and return only after the provider finishes the scan. This requires the separate Live Scanning product.

  • Create live scan task

    Start a non-blocking temporary Live Scan on a selected scanner and return its UUID immediately without waiting for completion. This external scan side effect requires the separate urlscan.io Live Scanning entitlement; a generic Pro plan may not include it.

  • Create saved search

    Create a reusable scans or hostnames search definition. This operation creates a persistent saved search and requires urlscan Pro; the hostnames datasource may require an additional product entitlement.

  • Create subscription

    Create a persistent scheduled or live alert subscription for saved searches. This Pro-only operation has external notification side effects: an active subscription can send email, invoke configured channels or webhooks, and create incidents. Confirm all recipients and channel or incident settings before calling.

  • Delete result

    Permanently delete a scan owned by the connected user or team. This destructive operation cannot be reversed and requires urlscan Pro.

  • Delete saved search

    Permanently delete a saved search by ID. This destructive operation cannot be undone and requires urlscan Pro saved-search access plus ownership or team write permission. Use it only for a saved search created or explicitly selected by the current workflow.

  • Delete subscription

    Permanently delete an alert subscription by ID. This destructive operation cannot be undone and requires urlscan Pro subscriptions access plus ownership or team write permission. Use it only for a subscription created or explicitly selected by the current workflow.

  • Fork incident

    Create a new Pro incident by copying an existing incident's configuration and complete stored state history. This creates a separate persistent incident; history volume and whether monitoring starts immediately are not documented.

and 10 more.

How to connect urlscan.io

  1. Sign in to Zeplik

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

  2. Connect urlscan.io

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

  3. Add your urlscan.io API key

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

Frequently asked questions

Can I use urlscan.io with Zeplik?
Yes. urlscan.io is available as an integration on Zeplik. Connect it once and the AI assistant can work with your urlscan.io account inside any conversation.
What can Zeplik do with urlscan.io?
Once connected, Zeplik has 29 read and 22 write actions for urlscan.io. Submit and retrieve website scans, search urlscan.io data, and manage urlscan Pro resources for threat intelligence and security investigations.
How do I connect urlscan.io to Zeplik?
You connect urlscan.io by pasting your own urlscan.io API key in Settings under Connectors. There is no separate app to install.
Does Zeplik change things in urlscan.io without asking?
No. Zeplik reads from urlscan.io by default. Any action that changes data in urlscan.io requires write access, which stays off until you enable it in Settings under Connectors.
How much does connecting urlscan.io cost?
Connecting urlscan.io is free. You only spend Zeplik credits when the assistant runs, and new accounts start with free credits.

Related business integrations

More on Zeplik

Connect urlscan.io to your AI assistant

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