Call Stored Procedure Activity
The Call Stored Procedure activity executes a specified stored procedure within a database. It processes input parameters and returns the resulting dataset. This activity is crucial for integrating database logic directly into automation workflows.
| Field | Description | Requirement |
|---|---|---|
| Connection Name | Specifies the name of the pre-configured database connection to use. | Required |
| Param1 | Defines the value for the first parameter of the stored procedure. | Optional |
| Param2 | Defines the value for the second parameter of the stored procedure. | Optional |
| Param3 | Defines the value for the third parameter of the stored procedure. | Optional |
| Param4 | Defines the value for the fourth parameter of the stored procedure. | Optional |
| Param5 | Defines the value for the fifth parameter of the stored procedure. | Optional |
| Parameters | Allows defining multiple parameters as a single array, overriding individual Param fields if specified. | Optional |
| Stored Procedure Name | The name of the stored procedure to execute, including placeholders for parameters. | Required |
| Result Dataset Name | A unique reference name for the dataset that will store the procedure's output. | Required |
Action Types & Examples
Parameter Array
- Format: Array of strings or nested arrays
- Example Result:
['1', 'STRING', 'in', '2314589']
Result Dataset Name
- Format: String
- Example Result:
employeesDataset
Implementation Examples
Field Setup - Connection name: robustaConnection - Stored procedure name: CALL robusta.getCustomerInfo(?,?); - Result dataset name: employeesDataset
Execution Parameters - Param1: ['1', 'STRING', 'in', '2314589'] - Param2: ['2', 'STRING', 'in', '${companyName}'] - Param3: ['3', 'STRING', 'in', '${companyName}'] - Param4: ['4', 'STRING', 'in', '${companyName}'] - Param5: ['5', 'STRING', 'in', '${companyName}'] - Parameters: [['1', 'STRING', 'in', '2314589'], ['2', 'STRING', 'in', '${companyName}']]
Technical Notes
When defining the
Stored Procedure Name, use a question mark (?) as a placeholder for each parameter that the procedure expects. The number of question marks must match the number of parameters being passed. For more detailed usage examples and advanced configurations, refer to the Using Stored Procedures Guide.