---
name: pulumi-setup-agent-automation
description: Create a schedule or event trigger for an existing Pulumi Agent, or pause or resume an automation. Use when the user requests recurring or event-driven agent work, says yes to a proposed schedule or trigger, or asks to pause or resume an automation.
title: pulumi-setup-agent-automation
canonical_url: https://skilld.dev/gh/pulumi/agent-skills/pulumi-setup-agent-automation
last_updated: 2026-11-18T13:18:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [references/cli-contract.md](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/references/cli-contract.md), [references/configure-automation.md](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/references/configure-automation.md), [references/recovery.md](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/references/recovery.md), [references/webhook-secrets.md](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/references/webhook-secrets.md), [use_cases.yaml](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/use_cases.yaml).
>
> If the user asked to install this Skill, run `npx skilld install pulumi/agent-skills/pulumi-setup-agent-automation`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/pulumi-setup-agent-automation`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/pulumi/agent-skills/pulumi-setup-agent-automation) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/pulumi-setup-agent-automation`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/pulumi-setup-agent-automation --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/pulumi-setup-agent-automation --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Set up agent automation

An automation runs a saved Pulumi Agent on a schedule or in response to events. Creating an automation does not create a new agent or start a one-time task.

## Create a schedule or event trigger

Read [Configure automation](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/references/configure-automation.md).

Confirm the organization, saved agent, per-run instructions, schedule or event, and CLI connections. Reuse choices the user already supplied and ask about anything needed to complete the request. If the user declined automation, leave the agent available for manual invocation.

Check the agent's `pausedAt` field. A paused agent starts no new runs even when its automation is active. Setting up or resuming an automation must not resume the agent.

Use the [API contract](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/references/cli-contract.md) for operations and request fields. For webhooks, read [Webhook secrets](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/references/webhook-secrets.md) before creating the automation.

## Pause or resume an existing automation

1. Discover and describe the read and pause operations in the [API contract](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/references/cli-contract.md). Read the automation by organization and ID.
2. For resume, verify the bound agent, its pause state, and the caller's invocation access. A missing or unreadable agent does not prevent an authorized automation pause.
3. If the automation already has the requested state, report it. Otherwise call `UpdateAgentAutomationV2Paused` with only the requested `paused` value.
4. Read back the automation to verify its state and unchanged rule. After resume, also report whether the agent is paused.

Pausing stops future recurrence; it does not cancel tasks already created. Resuming an automation does not resume its agent.

## Verify and report

Return the automation ID, bound agent, saved schedule or trigger, and automation state. If the agent is paused, say that it cannot start new runs.

Saving configuration does not prove that a webhook was delivered or a task completed. Do not trigger a test run unless requested.

For an uncertain create response or mismatched saved configuration, follow [Recovery](https://skilld.dev/api/skills-raw/pulumi/agent-skills/pulumi-setup-agent-automation/references/recovery.md). If a required API or decision is unavailable, preserve the draft and explain what is needed to continue.
