Before this feature, a webhook async execution always answer a body like this:

{"id":"cb045e6a-48e4-4bc4-a7be-a09bca0ffbe5","status":"CREATED","data":null}

Now, if a query param (async_response) is provided, that content will be the response body.

For example this request "cloud.yepcode.io/api/xxxx/webh... on it'" will respond Working on it. If we provide false as async_response, no body will be provided.

HTTP codes won’t be affected.

You can now modify an existing schedule directly instead of needing to delete it and create a new one. This makes adjustments much faster and smoother.

API Usage

• Use the updateSchedule endpoint in the Yepcode API to update schedules seamlessly
  
• Specify the schedule ID in the path and include your updated schedule details in the request body to modify the schedule.

We’ve improved our Local Disk feature, which lets your processes store and access files on the execution environment’s local filesystem. These enhancements make file handling faster, more reliable, and better integrated with other YepCode capabilities.

For more details, see our Local Disk documentation.

We’ve added YepCode Storage, a secure and integrated way to store and manage data directly from your YepCode projects. Use it to persist files, configuration, or intermediate results between executions without relying on external services.

For more details, see our official YepCode Storage documentation.

You can now install dependencies directly from Git repositories, not just from public package registries.

• Node.js: Git URLs
• Python: VCS support via pip

This allows you to use specific commits, branches, or repositories in your projects.

For more details, check our official documentation on dependencies.

Previously, if you hit your execution quota, new executions were rejected.
Now, they are automatically queued and will run once quota becomes available.

The maximum number of queued executions depends on your plan — some plans allow unlimited queuing.

YepCode MCP server allows AI platforms to seamlessly interact with YepCode infrastructure. This enables you to turn your YepCode processes into powerful tools accessible by AI assistants.

You can integrate the MCP server with platforms like Cursor or Claude Desktop using either:

• Remote mode – Use our hosted MCP SSE server, no installation required.
• Local mode – Run the MCP server locally using NPX or Docker.

Go to the Settings tab to view your current limits. For example:

You can compare all plan limits in docs.

The callback_url setting allows you to receive execution results upon completion, whether it was successful or failed. It is supported in the Execute Process (Sync), Execute Process (Async), and Schedule Process endpoints.

Since we added the ability to use dependencies in YepCode, it has created a maintainability challenge supporting all package versions with Credentials. As a result, we are deprecating them. You can still securely initialize your clients using environment variables. For example: