Deploy pipelines

In the SnapLogic Platform, tasks invoke pipelines and make them operational. After you design and test a pipeline locally, create a task to run it in production. Three types of tasks offer flexibility:

  • Scheduled Tasks: Use this option to perform a job at a specific time or interval, or on a complex schedule.
  • Triggered Tasks: Use this option to enable pipeline execution through an HTTP call. Triggered Tasks build a web API endpoint that allows data to be passed into and retrieved from a pipeline.
  • Ultra Tasks: Use this option for specialized, low-latency jobs that need to process documents continuously or for pipelines designed to be always-on. For low-latency jobs, a FeedMaster node in the Snaplex queues the incoming messages. The URL method is similar to triggered tasks, but the pipeline design limits specific Snaps. For always-on pipelines, the Ultra Task continuously polls the target messaging service, making it preferable to a scheduled task.

Task authentication

Triggered and Ultra tasks support the following four authentication mechanisms:

  • Basic Auth using Service Accounts: The simplest method, shared across tasks based on user ACLs, supporting password expiration.
  • Bearer Token: Easy to use, with one unique token per task by default. Tokens can be manually synced across tasks.
  • JWT-based Access Control: Appropriate for Ultra Tasks, implemented using JWT Snaps for fine-grained access control at the project level or based on other criteria, allowing multiple tokens per task.
  • API Policy Manager: Offers various authentication and authorization policies like Callout Authenticator and Generic OAuth policies.

Task permissions

SnapLogic tasks use the same permissions as other project assets. As an Environment admin or task creator, you can set the following permissions for other users at the project level:

  • Read Only: View task configuration and details.
  • Read & Write: View and modify the task but cannot run it.
  • Read & Execute: View and run tasks but cannot change configuration or details.
  • Full Access: View, run, and modify tasks.
  • Owner: Modify permissions on a task, in addition to all of the above.

If a user or group has different permissions at different levels, the lowest permission level is enforced. For example, if you have Read & Execute permissions to the Project Space containing the task but only Read permissions to the project, you cannot run the task.

Anyone with the bearer token can execute a Triggered or Ultra task. The task owner is the user who executes the pipeline when the task is invoked.

Task notifications

When creating or updating a task, you can configure email and Slack notifications based on status. For example, a task owner might enter themselves as a recipient and select "Stopped" as the event type. Environment admins can also create email and Slack notifications based on task duration. create-notifications.html describes how to configure task notifications based on status and duration.