ceven

Uploadcare

Automates the lifecycle of your assets by managing uploads, processing image transformations, and syncing file metadata across your tech stack.

Try Uploadcare in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Uploadcare integration

    • Describe the outcome and Ceven picks the right Uploadcare 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 Uploadcare data, across all 34 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Uploadcare 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 Uploadcare, when, and on whose behalf.
    • The agent pauses and asks when Uploadcare is unclear instead of plowing ahead.

  4. Enterprise grade security

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

Supported tools

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

Create webhook
Use this when you need to subscribe to file events and receive notifications at your service. Ensure you have a project uuid first.
Delete metadata key
Use this when you need to remove obsolete metadata from an uploadcare file after processing is complete.
Delete webhook
Use this when you need to remove a specific webhook by its id after confirming the details.
Get download url
Pull a temporary download url for a file. Use this when you need a direct link after a file is uploaded.
Get file info
Pull detailed metadata and usage information for a specific file. Use this after uploading to verify asset details.
Get project info
Pull current project configuration details. Use this to verify project settings and limits.
List files
Pull a list of files in a project. Use optional filters or pagination to find specific assets.
List groups
Pull a paginated list of file groups in the project to organize assets.
List webhooks
Pull a paginated list of all active webhook subscriptions for your project.
Rotate image
Rotate an image by 90, 180, or 270 degrees clockwise. Use this after confirming the file uuid.
Store file
Mark a file as permanently stored. Use this to prevent the file from being deleted by automatic cleanup.
Mirror image
Mirror an image horizontally via the CDN. Use this to get a url for a flipped version of an asset.
Create Uploadcare webhook
Tool to create a new webhook. use when you need to subscribe to file events and receive notifications at your service. ensure you have an existing project uuid before using this tool.
Delete File Metadata Key
Tool to delete a specific metadata key from an uploadcare file. use when you need to remove obsolete metadata after file processing.
Get Uploadcare File Download URL
Tool to retrieve a temporary download url for a file. use when you need a direct download link after uploading a file.
Get Uploadcare File Info
Tool to get information about a specific file. use after uploading a file to retrieve detailed metadata and usage information.
Get Uploadcare Project Info
Tool to get information about the current uploadcare project. use when you need to retrieve project configuration details.
List Uploadcare Files
Tool to list files in a project. use when you need to retrieve uploaded files with optional filters, pagination, or include total count.
List Uploadcare Groups
Tool to list groups in the project. use when you need to retrieve paginated groups of files.
List Uploadcare Webhooks
Tool to list webhook subscriptions. use when you need a paginated list of webhooks for your project after configuring authentication.
Store Uploadcare File
Tool to mark an uploadcare file as permanently stored. use after uploading a file when you need to store it permanently.
Mirror Uploadcare Image
Tool to mirror an image horizontally via uploadcare cdn. use when you need the url of a horizontally flipped image.

22 actions · scroll to see them all

Frequently asked questions

Uploadcare often treats newly uploaded files as temporary until they are explicitly stored. Ceven manages this by using the Store File action within your workflow. You can set up a trigger so that any file meeting certain criteria, such as being uploaded to a specific group or having a certain metadata tag, is automatically marked for permanent storage. This prevents the loss of critical assets that would otherwise be purged by the system. The agent can also monitor your storage usage by pulling project info and alerting you when you approach your plan limits, ensuring your production assets remain available to your users without interruption.
Ceven leverages the Uploadcare CDN and API to perform specific transformations like rotating and mirroring. While it cannot perform manual brush work or complex retouching, it can automate the application of CDN parameters to your image urls. For example, you can tell the agent to generate mirrored versions of all product shots for a specific category. The agent handles the API call to rotate or mirror the image and then saves the resulting url to your database. This allows you to maintain a single source file while serving multiple processed versions to your end users based on the specific needs of your layout.
Setting up webhooks is a straightforward process within the Ceven workflow builder. You use the Create Webhook action to tell Uploadcare which events should trigger a notification and where that notification should be sent. You will need a destination url capable of receiving POST requests. Once the webhook is active, Uploadcare sends a payload every time a file event occurs. Ceven can then catch these events to trigger further actions, such as updating a record in your CRM or sending a notification to a Slack channel. You can manage these subscriptions using the List Webhooks and Delete Webhook actions provided in the toolkit.
Ceven can both read and modify metadata keys attached to your Uploadcare files. This is useful for adding context like product SKUs or photographer names to an image without changing the file itself. Use the Get File Info action to pull existing metadata and the Delete Metadata Key action to clean up obsolete tags. By syncing this metadata with your internal systems, you can create a searchable index of your assets. For instance, the agent can scan your files for a specific metadata key and then move all matching files into a specific Uploadcare group for better organization and easier retrieval.
Uploadcare uses pagination for listing files and groups to ensure API performance. Ceven handles this by automatically walking the cursor through the paginated results. However, you should be aware that very large projects with millions of files may encounter API rate limits if you attempt to list every file in a single synchronous run. To avoid this, we recommend using filters or organizing files into groups. By narrowing the scope of the List Files call, the agent can retrieve data more efficiently and avoid the throttling limits imposed by the Uploadcare API on high volume accounts.
These actions do not modify the original source file stored in the Uploadcare cloud. Instead, they utilize the Uploadcare image processing API to create a transformed version of the image delivered via the CDN. When Ceven calls the Rotate Image or Mirror Image action, it is essentially requesting a specific transformation be applied to the asset. The resulting url provided by the API contains the instructions for the CDN to process the image on the fly. This means your original high resolution upload remains untouched, while your users receive the optimized, rotated, or mirrored version they need for the interface.
Ceven works with any Uploadcare project as long as you have the necessary API credentials and permissions. However, some features available in the API may be gated by your specific Uploadcare pricing tier. For example, certain advanced processing options or higher rate limits are only available on paid plans. If an action fails with a permissions or tier error, it is likely because the Uploadcare account does not have that feature enabled. We recommend checking your Uploadcare dashboard to ensure your plan supports the specific API calls your Ceven workflows are attempting to execute for your asset management.
Yes, Ceven can manage the organization of your files using the List Groups and List Files actions. While the current toolset focuses on retrieval and modification, you can build workflows that identify files based on their metadata or name and then use the API to categorize them. For example, the agent can look for any file with the word draft in the name and ensure it is not marked for permanent storage, while files marked final are moved to a production group. This keeps your Uploadcare project clean and ensures that only approved assets are being served to your customers through the CDN.

Alternatives to Uploadcare

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

Cloudinary logoCloudinaryImgix logoImgixAWS S3 logoAWS S3

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Uploadcare 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