Build Zapier automations that keep your docs current

The Promptless Submit Documentation Task action in Zapier sends a documentation task to Promptless from any Zap. Promptless researches the task, writes the change, and opens one pull request per task for you to review. If the page doesn’t exist yet, Promptless drafts it.

For the fields the action sends, see API triggers.

Update buyer persona profiles from call recordings

Use this recipe to update the buyer persona profiles in your docs after each sales or discovery call. Promptless reads these profiles when it writes marketing pages.

Start the Zap with a new meeting transcript from your call recorder, such as Grain, Fathom, Gong, or Zoom. Any recorder with a Zapier trigger for new transcripts works.
Optional: Add a filter step that passes only sales and discovery calls. Without the filter, internal meetings also start a persona profile update.
Add the Submit Documentation Task action. In What Changed, ask Promptless to update the buyer persona profiles from the call. List what to capture: the objections prospects raised, the words they used for the problem, the alternatives they compared, and the outcomes they cared about.
In Supporting Context, add a label and value for each of these details: the call date, the account name, and a link to the recording. Reviewers use these to trace a persona claim back to its call.

Update comparison pages when competitors change

Use this recipe to check competitor pages on a schedule and update the comparison pages that their changes affect.

Start the Zap with Schedule by Zapier. Every two weeks is a reasonable starting interval.
Add a step that reads the competitor pages you track. Use a page-monitoring or scraping app from Zapier’s app directory, or use Webhooks by Zapier with a scraping service you run.
Add the Submit Documentation Task action. In What Changed, ask Promptless to update the comparison pages that the scraped changes affect.
In Supporting Context, pass the scraped content, the page URL, and the date you scraped it.

Send the full scraped content and let Promptless decide what changed. Promptless opens a pull request only when it finds a change worth documenting, so a scrape with nothing new opens no pull request.

Other recipes

You can send these events to the Submit Documentation Task action:

A recurring theme in support tickets from your helpdesk, to fill the gap in the docs.
A deal that moves to closed-won in your CRM, to update the related case study or proof point.
A published product release note, to update the marketing pages for that capability.

Set up Zaps for focused results

Set Doc Collection in the action when a recipe always changes the same docs. A collection is a set of docs that Promptless maintains. If you leave the field blank, Promptless chooses the collection, so check which collection each pull request targets.
Start a new recipe against one collection, and add more after it works. For a structured trial, see Run a pilot.
In What Changed, name the page and what changed about it. A task such as “update the docs” gives Promptless too little to go on.
Each task opens one pull request. Nothing changes in your docs until you merge it.

For help building a Zap, email help@gopromptless.ai.