To connect and automate SnapLogic® as part of a chain, add a step that includes a SnapLogic connection command. For example:
- Run SnapLogic pipelines
- Query run history
- Get run log content for further analysis
To enable these commands, an IT admin first sets up a SnapLogic connector.
Get logs
To retrieve the logs for a pipeline run, use a Get logs command.
Properties
Property |
Detail |
Run ID (RUUID) |
Enter the run ID (RUUID) of the pipeline. |
Log level |
Select the level of logs to see. |
Outputs
Output |
Output type |
Log file |
File |
Response headers |
JSON |
Response code |
Integer |
Exit codes
Code |
Type |
Detail |
0 |
Success |
Success |
2 |
Error |
Task failed |
Query runs
To retrieve the previous pipeline run data, use a Query runs command.
Properties
Property |
Detail |
Limit |
Enter the number of runs to return. |
In last hours |
Enter how many of the previous hours—to now—to query. |
Pipeline name |
Enter the name of the pipeline to query. |
State |
Select the state of the pipeline run to query: NoUpdate, Prepared, Started, Queued, Stopped, Stopping, Completed, or Failed. |
Outputs
Output |
Output type |
Response body |
File |
Response headers |
JSON |
Response code |
Integer |
Exit codes
Code |
Type |
Detail |
0 |
Success |
Success |
2 |
Error |
Task failed |
Run pipeline
To dispatch a request to start a pipeline, use a Run pipeline command.
Properties
Property |
Detail |
Task URL |
Enter the URL of the triggered task. |
Pipeline name |
Enter the name of the pipeline, for the Run ID output. |
Outputs
Output |
Output type |
Response body |
File |
Response headers |
JSON |
Response code |
Integer |
Run ID |
String |
Exit codes
Code |
Type |
Detail |
0 |
Success |
Success |
2 |
Error |
Task failed |
3 |
Warning |
Unable to provide the Run ID output |