Ploybooks

Last updated October 20, 2026

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 — Set a plain-language cadence and a Ploybook can run on its own while the schedule is enabled.
• 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 chat

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, 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.

Find a Ploybook from Overview

1. Open Overview, then Ploybooks.
2. Choose Suggested to browse suggestions or Scheduled to find scheduled workflows.
3. Preview a card to inspect the Ploybook before taking action.
4. Choose Open Ploybook to open its page for review, or Run Ploybook when you want the work to start.

Run Ploybook starts work and uses AI credits. Opening the Ploybook for review is different from running it. If Ploybooks is not visible in your workspace, check with your workspace administrator before following this path.

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 chat 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.

Start from a template

The Ploybook library has ready-made Ploybooks you can run as they are or copy and adapt. Open Library, then Ploybooks, and choose Explore library. Choose a category tab, such as SEO, Content, or Conversion, to see only those Ploybooks, or All to see every one. The tabs hide while you search. Open a template to read its steps, then choose Run, or choose Customize to make your own editable copy in this workspace. Running a template uses AI credits.

• Website health and usability audit: finds broken pages, missing images, and usability bugs on your live site. It checks every public page it finds automatically, on desktop and mobile, then looks more closely at your main layouts and key visitor paths. It writes a short report in Docs with each confirmed problem, the pages it affects, and how to fix it, and it says which pages it reviewed closely. Repeated issues are grouped together. It only reads your site and changes nothing. It always runs on Ploy Agent.
• Build a Content Library: finds new interviews, podcasts, articles, and posts from your company's people, and can include internal resources you choose, such as customer calls and demos. Your team approves each item before it is saved to a database, with source links and full transcripts where available. Reviews can go to a Slack channel you pick or to a document.
• ABM Page for a Named Account: researches one company and its buyer, then builds a private outreach page in your brand. The page opens with something the company did recently, proposes two or three things you will do for them, and backs them with one of your customer stories, or a mockup labelled Proposed page when no story fits. Use it when you have a specific company in mind.
• ABM Page for an Audience Segment: builds a page for an industry, role, or company type, using your site's own brand and proof. It stays out of search results.
• Enhance an Existing Website: makes your current site look better while it keeps your brand. It starts with your homepage unless you name another page. It asks a few questions about your business, tells you the direction and fonts it chose, and then builds the improved page. To keep your current wording, ask it to keep your copy word for word.
• Add an Effect: adds a Paper Shaders background, image filter, or logo animation to a page and tunes it to your design tokens. Effects is rolling out, so this Ploybook appears only in workspaces where it is enabled. See Ploy Effects.

Scheduling a Ploybook

Set a recurring schedule in plain language. You do not need to enter a cron expression.

1. Go to Library, then Ploybooks, and open the Ploybook.
2. Choose Schedule a Ploybook if it has no schedule, or Add Schedule if schedules already exist.
3. Under When should this run?, enter a cadence such as "every weekday at 9am" and check the timing preview.
4. Choose Timezone. Review Starts (optional) and Ends (optional).
5. Set Enable schedule, review the displayed AI credit notice, then choose Save.
6. Verify that the saved schedule appears in the list with the intended timing and enabled status.

A new schedule ends 90 days after it starts, at midnight in the schedule's timezone. The end date is filled in for you, and you can change it or clear it for no end date. The same default applies when you ask Ploy's Agent to schedule a Ploybook. Runs stop at the end date. Three days before a schedule ends, the person who created it gets a notification, with a link to extend the end date. If that person has left the workspace, the workspace owner gets the reminder. Without an end date, an enabled schedule can keep using AI credits until you disable it.

The displayed credit notice explains that scheduled runs use AI credits. Check it before enabling a recurring run, especially if you clear the end date.

If a required integration is missing for the person whose account runs the schedule, connect that account or edit the Ploybook's requirements before enabling it. See Integrations for connection types and permissions.

You can add more than one schedule to a Ploybook and change or disable a saved schedule later.

Schedule a future production publish

A scheduled Ploybook can prepare a production publish or publish at its run time when publishing is part of the workflow. Scheduling a Ploybook does not make every run publish automatically.

Before scheduling a workflow that should publish to production, an owner or admin must allow automatic publishing to production in Site → Advanced. If that permission is not enabled when the scheduled run reaches the publish step, the run must stop for a manual publish instead. See Publishing & Deploys for setup details.

Working memory

Working memory is optional. When enabled, recurring Ploybook runs can reuse a shared working document so the work builds on useful context from earlier runs. Custom Ploybooks start with working memory turned off.

It is useful for recurring research, content, and operational workflows where prior findings or decisions should carry forward. Enable it only when retaining context from earlier runs helps the next run do better work.

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.