Ploybooks

Save a workflow once, then run it again — on demand or on a schedule.

A Ploybook is a reusable, step-by-step playbook that Ploy's Agent follows to get a job done. Think of it as a saved recipe for work you do more than once — build an ABM landing page for a prospect, draft replies to new contact-form submissions, post a weekly traffic report to Slack. Instead of re-explaining the process every time, you capture it as a Ploybook and run it whenever you need it, or put it on a schedule so it runs itself.

What a Ploybook Is

Every Ploybook is a plain-language guide — broken into phases and checklist steps — that describes the outcome you want and how to get there. When you run one, Ploy's Agent reads the guide and executes the steps with the same tools it uses in a normal chat: building pages, researching, querying analytics, drafting emails, calling your connected integrations, and more.

• Reusable — Written once, run any number of times with fresh inputs.
• Adaptable — A Ploybook is a guide, not a rigid macro. Ploy's Agent adapts each run to the specific context, account, or data it's given.
• Schedulable — Attach a schedule and a Ploybook runs on its own — hourly, daily, weekly, or any cron cadence.
• Triggerable — Wire a Ploybook to a Webhook so an external event (a new lead, a closed deal, a CMS change) kicks it off automatically.

Tip: If you find yourself typing the same multi-step request into Ploy's Agent more than once, that's a Ploybook waiting to happen.

When to Use One

Ploybooks shine anywhere a process repeats. A few patterns teams reach for:

If a task is genuinely one-off, you don't need a Ploybook — just ask Ploy's Agent directly. Reach for a Ploybook when the shape of the work stays the same and only the inputs change.

Creating a Ploybook from a Ploy Conversation

The easiest way to author a Ploybook is to let Ploy's Agent generalize work you've already done. Run the task once in a normal chat (a ploy), confirm the result is what you want, then ask Ploy's Agent to save it:

• "Save this as a Ploybook so I can run it again next week."
• "Turn this workflow into a reusable Ploybook for any prospect."
• "Make a Ploybook out of what we just did, but parameterize the company name."

Ploy's Agent rewrites the specific run into a generalized, phased guide — replacing the concrete details (company names, URLs, dates) with placeholders so each future run takes fresh inputs. After a piece of work wraps, Ploy's Agent will often offer to save it as a Ploybook on its own; just say yes.

You can also create one from scratch by describing the workflow in plain language:

• "Create a Ploybook that pulls yesterday's ad spend across Meta and Google and posts a summary to Slack."

Review before you rely on it. A freshly authored Ploybook is a draft. Read through its steps once and do a test run before scheduling it or pointing it at live data — the same way you'd review any teammate's runbook.

Running a Ploybook

Once saved, a Ploybook can run three ways:

1. On demand — Ask Ploy's Agent to run it ("Run the ABM page Ploybook for Acme Inc."), or launch it from your saved Ploybooks. Each run happens in its own ploy so you can watch the steps and review the output.
2. On a schedule — Attach a recurring schedule and it runs automatically (see below).
3. On a trigger — Wire it to a Webhook so an external event runs it with the event payload as context.

Scheduling a Ploybook

Any Ploybook can run on a recurring schedule — no one has to remember to kick it off. A schedule is a cron expression plus a timezone, so reports land before your team's morning and digests fire at the right local hour.

The simplest way is to just ask:

• "Run this Ploybook every weekday at 9am Eastern."
• "Schedule the traffic digest for Mondays at 7am Pacific."
• "Run the contact-reply Ploybook twice a day, at 9am and 5pm."

Ploy's Agent translates that into a schedule and wires it up. Under the hood, a schedule is:

A Ploybook can have more than one schedule — for example a single digest Ploybook that posts a daily summary every morning and an extended week-over-week summary on Mondays. You can update the cadence, change the timezone, pause, or delete a schedule any time by asking Ploy's Agent.

Tip: Scheduled runs happen in the background and produce their own ploy each time, so you always have a record of exactly what ran and what it produced.

Managing & Editing Ploybooks

Ploybooks are living documents — refine them as your process evolves:

• Edit — "Add a step to the ABM Ploybook that writes the published URL back to the CRM."
• Rename or re-scope — Update the title, description, and tags so the right Ploybook is easy to find later.
• Delete — Remove a Ploybook you no longer use. (Schedules attached to it stop too.)

Because each run executes against the current version of the guide, improving a Ploybook once improves every future run — manual, scheduled, and triggered alike.

Keep a human in the loop for anything that sends. For Ploybooks that draft outbound email or post publicly, have them produce drafts for review rather than auto-sending. Review the steps before scheduling, and start a new Ploybook against test data first.

Ploybooks & Webhooks

Schedules answer "run this on a clock." Webhooks answer "run this when something happens." Wire a Ploybook as the trigger on a webhook endpoint and every accepted event runs the Ploybook with the payload injected as context — so a new enriched lead, a closed deal, or a CMS update can kick off a full workflow with no one at the keyboard. See Webhooks for the full setup.

What's Next?

• Meet your operator — Ploy's Agent is what runs every Ploybook — start there for how to work with it.
• Trigger on events — Use Webhooks to run Ploybooks from external systems.
• Connect your tools — Browse Integrations for the services a Ploybook can act on.
• Get help — Check the FAQ & Troubleshooting page if a run doesn't go as expected.