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:
You can now manage API credentials directly from the API Credentials tab in your team settings. These credentials can be used for the REST API or YepCode Run.
Configure your preferred AI assistant to help you build your processes.
JavaScript processes are now executed in Node.js 22.x.
Dependencies will be global for your team by default, but if you need to use process scoped dependencies, you may do that enabling the flag under process dependencies settings:
Manage your process tags using YepCode REST Api.
Use the @add-package
comment to manually add a dependency to your process. To specify a version, use the syntax: @add-package <package-name>=<version>
. See the documentation for details. For example:
To prevent breaking active schedules, webhooks, or forms that trigger a process execution, modules referenced in any process can no longer be renamed or deleted. Attempting to do so will display an error message:
Or if you are using Rest Api: