Actions2
Overview
The node "YepCode" allows you to run complex business logic by executing predefined processes or dynamic scripts within your n8n workflows. Specifically, the Run Process operation lets you trigger YepCode processes with customizable input parameters, enabling flexible integration with APIs and services through real code without managing infrastructure.
Common scenarios include:
- Automating multi-step business workflows defined as YepCode processes.
- Running server-side logic that requires dynamic inputs from workflow data.
- Integrating external APIs or services via YepCode processes for advanced data manipulation.
- Using synchronous or asynchronous execution modes depending on whether you need immediate results.
For example, you might use this node to run a customer onboarding process defined in YepCode, passing user data collected earlier in the workflow, and then proceed based on the process outcome.
Properties
| Name | Meaning |
|---|---|
| Mode | Determines how the process runs relative to input items: - Run Once for All Items: Executes the process a single time regardless of the number of input items. - Run Once for Each Item: Runs the process separately for each input item. |
| Process | The specific YepCode process to execute. You can select from a searchable list or specify an ID using an expression. |
| Parameters | Maps input data to the process form fields. This allows you to define how workflow data is passed as parameters to the YepCode process. |
| Show Advanced Options | Toggles visibility of additional configuration options. |
| Add n8n Context as Parameters | When enabled, adds the n8n execution context (input items, environment variables, execution info) to the process parameters under yepcode.context.parameters.n8n. Useful for accessing workflow metadata inside the process. |
| Version | Specifies which version of the YepCode process to run. You can choose from available version tags or specify one via expression. |
| Synchronous | If true, the node waits for the process execution to complete and returns the result. If false, it triggers the process but does not wait for completion, so no result is returned. |
| Initiated By | A meta attribute string to identify who initiated the process execution. Can be used for logging or tracking purposes. |
| Comment | A meta attribute string to add comments to the process execution for documentation or audit trails. |
Output
The node outputs JSON data representing the result of the executed YepCode process. This typically includes the process execution status, any output data produced by the process, and metadata such as execution IDs or timestamps.
If the process is run synchronously, the output contains the full execution result. If run asynchronously, the output may not contain execution results since the node does not wait for completion.
The node does not explicitly handle binary data output.
Dependencies
- Requires an API key credential to authenticate with the YepCode service.
- Depends on the YepCode platform to host and run the defined processes.
- The node uses internal methods to load available processes and their versions dynamically.
- No additional environment variables are required beyond the API authentication.
Troubleshooting
Common issues:
- Selecting a non-existent or unpublished process will cause errors.
- Incorrect parameter mapping may lead to process failures or unexpected behavior.
- Running asynchronously means no output result is returned; users expecting output must enable synchronous mode.
- Network or authentication errors if the API key is invalid or connectivity to YepCode service is interrupted.
Error messages:
"The operation \"run_process\" is not supported!"— indicates an unsupported operation was requested; ensure the operation parameter is set correctly.- Errors related to missing or invalid process IDs or versions usually indicate misconfiguration in the "Process" or "Version" properties.
- Parameter validation errors occur if input data does not match the expected schema of the process form.
To resolve these, verify process existence, check parameter mappings, confirm API credentials, and ensure network connectivity.