ceven

Apify

Triggers web scraping actors to pull live data from any website, stores results in datasets, and routes the extracted data into your CRM or database automatically.

Try Apify in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Apify integration

    • Describe the outcome and Ceven picks the right Apify calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Apify data, across all 112 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Apify access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Apify, when, and on whose behalf.
    • The agent pauses and asks when Apify is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Apify.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Apify action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Apify, and when to use it.

Run Actor Sync
Use this when you need immediate results from a scraper and can wait up to 300 seconds for the response.
Run Actor Asynchronously
Trigger a scraper to start and return the run ID immediately. Use this for long running crawls.
Get dataset items
Pull the extracted data from a specific dataset. Use this to fetch the final results of a scraping run.
Create Actor Task
Set up a named configuration for an actor. Use this to save specific scraping settings for recurring use.
Run Task Asynchronously
Start a previously configured actor task without needing to pass the full input again.
Store Data in Dataset
Push custom data items into an Apify dataset. Use this to enrich scraped data with external info.
Create Task Webhook
Set up a notification that fires when a task finishes. Use this to trigger downstream Ceven workflows.
Get Key Value Record
Fetch a specific piece of data from a key value store by its key name.
Store Data in Key Value Store
Save a JSON object to a key value store. Use this for persisting state between different actor runs.
Get log
Retrieve the execution logs for a run. Use this to debug why a scraper failed to find elements.
Update Task Input
Change the settings or target URLs for an existing task without creating a new one.
Get Actor Details
Pull metadata about a specific actor including its description and version.
Create Actor
Tool to create a new actor with specified configuration. use when you need to initialize a fresh actor programmatically before publishing or running it.
Create Dataset
Tool to create a new dataset. use when you need to initialize or retrieve a dataset by name.
Delete Actor
Tool to delete an actor permanently. use when you need to remove an actor by its id or username~actorname. confirm before calling.
Delete Webhook
Tool to delete a webhook by its id. use when removing a webhook after confirming the webhook id.
Get all webhooks
Tool to get a list of all webhooks created by the user. use when you need to enumerate webhooks before filtering or maintenance.
Get Default Build
Tool to get the default build for an actor. use after specifying the actor id; optionally wait for the build to finish before returning.
Get list of builds
Tool to get a list of builds for a specific actor. use when you need paginated access to an actor’s build (version) history.
Get list of runs
Tool to get a list of runs for a specific actor. use when you need to paginate through runs and optionally filter by status before processing run data.
Get list of task runs
Tool to get a list of runs for a specific actor task. use when you need to paginate through task runs and optionally filter by status.
Get list of tasks
Tool to fetch a paginated list of tasks belonging to the authenticated user. use when you need to browse or sort tasks created by the user.
Get list of task webhooks
Tool to get a list of webhooks for a specific actor task. use when you need to review or paginate webhooks after creating or updating a task.
Get OpenAPI Definition
Tool to get the openapi definition for a specific actor build. use when you need the api schema for code generation or analysis.
Get Task Input
Tool to retrieve the input configuration of a specific task. use when you need to inspect stored task input before execution or debugging.
Resurrect Run
Tool to resurrect a finished actor run. use when you need to restart a completed or failed run. deprecated endpoint; may be removed in future.
Run Actor Sync & Get Dataset Items
Tool to run an actor synchronously and retrieve its dataset items. use when immediate access to run results is needed.
Update Key Value Store
Tool to update a key value store's properties. use when renaming or changing access or schema version of the store after confirming the store id.

28 actions · scroll to see them all

Frequently asked questions

Ceven uses the asynchronous run action for any actor expected to take more than a few minutes. When the agent triggers an asynchronous run, it receives a run ID and can either poll the status using the run list tool or wait for a webhook notification. If you use the synchronous run tool, the connection will timeout after 300 seconds because of Apify API limits. For large scale crawls that take hours, we recommend creating a task webhook. This allows Apify to ping Ceven the moment the data is ready, which then triggers the next step in your workflow to process the dataset.
Yes. Ceven can interact with both Apify datasets and key value stores. If your workflow involves gathering data from multiple sources, the agent can use the store data in dataset tool to aggregate everything in one place before you export it to a spreadsheet or CRM. Key value stores are particularly useful for storing small pieces of state, such as the last processed page number or a session cookie, ensuring that subsequent actor runs can pick up exactly where the previous one left off without duplicating work or triggering bot detection.
The agent monitors the status of every run it initiates. If an actor returns a failed status, Ceven can be configured to pull the execution logs using the get log tool. The agent analyzes the log for common errors like selector changes or proxy blocks and can then notify you with the specific error message. You can build a recovery loop where the agent attempts to update the task input with a different proxy configuration or notifies a developer to update the scraper logic before attempting the run again.
Ceven connects to Apify using a secure API token. You provide the token in the integration settings, and it is stored encrypted at rest. This token is passed in the authorization header of every request made to the Apify API. The agent never exposes this token in the logs or to the end user. You can rotate your token in the Apify console at any time, and you simply need to update the token in the Ceven connection panel to restore service to your workflows.
Ceven respects Apify pagination limits. When pulling items from a dataset, the agent requests data in batches to avoid memory overflows and API timeouts. If a dataset contains millions of records, the agent will walk through the pages using the offset and limit parameters. For extremely large datasets, we recommend using the store data in dataset tool to filter results within Apify first, or using a specialized export actor to move the data to a cloud storage bucket that Ceven can then read from more efficiently.
Ceven can create the shell of an actor and configure its settings using the create actor tool, but it does not write the underlying JavaScript or Python code for the scraper itself. You should develop and test your actor logic within the Apify console or via their CLI. Once the actor is published to the Apify Store or your private account, Ceven can manage its lifecycle, trigger its runs, modify its inputs, and handle its output. This separation ensures that the complex logic of web scraping remains version controlled in your code repository.
Yes. Ceven can create and manage task webhooks. This is the most efficient way to run scraping workflows. Instead of having the agent poll Apify every few minutes to see if a run is finished, which wastes API quota, the agent sets up a webhook. When the actor completes its task, Apify sends an HTTP POST request to a unique Ceven endpoint. This immediately wakes up the workflow, allowing the agent to fetch the dataset items and push them to your destination system without any unnecessary delay.
The most common issue is the dynamic nature of web pages. If a website changes its HTML structure, the Apify actor will return empty results or fail, and the AI agent might misinterpret this as a system error rather than a scraping error. Another quirk is the Apify compute unit consumption. Complex actors using headless browsers consume compute units much faster than simple HTTP scrapers. If your account runs out of compute units, the API will return a 402 payment required error, which will cause the Ceven workflow to halt until you add more credits to your Apify plan.

Alternatives to Apify

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

Bright Data logoBright DataOctoparse logoOctoparseZyte logoZyte

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Apify and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free