Automation

Documentation Index

Fetch the complete documentation index at: https://docs.poolside.ai/llms.txt

Use this file to discover all available pages before exploring further.

​

Overview

Object	What it does
Task	Defines what to run: an agent session with a specific agent, sandbox, and prompt. A task is independent of its trigger.
Schedule	Defines when to run it: a cron-based trigger that starts one or more tasks at defined intervals.
Webhook endpoint	Defines when to run it: an HTTPS endpoint that receives external events and routes matching requests to pipeline builds through webhook actions.

​

Create a task

• You can access Orchestration > Tasks in the Poolside Console.
• A managed agent exists for the task.
• A sandbox definition exists for the task. The sandbox controls the execution environment for the agent session.

1. In the Poolside Console, navigate to Orchestration > Tasks.
2. Click New Task.
3. Enter a Name.
4. Optional: Enter a Description.
5. For Type, select Agent Session.
6. Select an Agent. This is the managed agent that runs when the task executes.
7. Select a Sandbox Definition. This controls the compute environment for the agent session.
8. Enter the Prompt to send to the agent when the task runs.
9. Click Save.

​

Create a schedule

• You can access Orchestration > Schedules in the Poolside Console.
• At least one task exists.

1. In the Poolside Console, navigate to Orchestration > Schedules.
2. Click New Schedule.
3. Enter a Name.
4. Enter a Cron Expression using standard cron syntax. For example, 0 9 * * 1-5 runs at 9:00 AM every weekday.
5. Optional: Enter a Description.
6. Click Create Schedule.
7. Open the schedule.
8. In Tasks, click Add Task and select the task you want to run on this schedule.

​

Set up a webhook endpoint

• You can access Orchestration > Webhooks in the Poolside Console.
• You know the external provider’s webhook signing format, including the hash algorithm and how it encodes the signature.

1. In the Poolside Console, navigate to Orchestration > Webhooks.
2. Click New Webhook Endpoint.
3. Enter a Name.
4. In Signing secret, copy the generated Secret value and store it securely. You need this value to configure the external provider.
   Copy the signing secret now. Poolside stores it as a credential and does not show the value again after you leave this page.
5. Select the Hash Algorithm and Encoding that match the external provider’s signing format.
6. Enter a Signature Value Expression that extracts the signature from the incoming request. For example, for a provider that sends the signature in an X-Signature header: headers["X-Signature"].
7. If Encoding is not Plain Text, enter a Signature Data Expression that specifies what data the provider signs.
8. Enter a Delivery ID Expression that extracts a unique identifier from the request. Orchestration uses this to prevent duplicate processing. For example: headers["X-Request-Id"].
9. Optional: Add Custom handlers for provider-specific handshakes. Some providers, such as Slack, send a URL verification challenge that must return a specific response before the endpoint is active.
10. Click Save.
11. Open the endpoint and copy the generated webhook URL. It follows the pattern: POST /v0/bridge/webhook-endpoints/<webhook-endpoint-id>.
12. In the external provider’s settings, add the webhook URL and signing secret.

​

Configure webhook actions

​

Related resources

• Orchestration overview
• Bridge SDK
• Pipelines
• Managed agents
• Sandboxes