Poily Docs
Poily · Developer docs

Connect your product to Poily

Docs for developers and AI agents connecting a product to a Poily portfolio. Your product keeps its own stack; each connection point is one place where it exchanges something with Poily.

Read the integration guide Use an agent prompt

Inside Connect your product

  1. 1. People — push your members (live)
  2. 2. Forms — capture signups on your site (live)
  3. 3. Blog / content — two ways to serve it (live)
  4. 4. Email & consent — what Poily handles for you (live)
  5. 5. Coming next

All pages

GuidesConnect your productThe umbrella guide: every connection point between your product and Poily (people push, forms, blog/content, email & consent)./connect · /connect.mdGuidesForms integrationPut a Poily-connected form on any site: iframe embed, <poily-form> web component, SDK / native form, and scan-to-create import./forms · /forms.mdAgent promptsPrompt: scan-to-create importFill-in-the-blanks prompt that wires a site's existing native <form> to Poily's scan-to-create import in one pass./prompts/import · /prompts/import.mdAgent promptsPrompt: <poily-form> high-fidelityFill-in-the-blanks prompt that renders a published Poily form with the <poily-form> web component, styled to the site's brand./prompts/high-fidelity · /prompts/high-fidelity.md

Built for agents too

Every page has a raw Markdown version at the same path plus .md, served as text/markdown with open CORS. /llms.txt lists them all, and /llms-full.txt puts every page in one file. URLs are stable, so it's safe to put them in prompts.

curl https://docs.poily.com/llms.txt
curl https://docs.poily.com/connect.md

These docs are public. API keys aren't: your portfolio operator issues them in the Poily console (app.poily.com → Settings → Connections). Questions or corrections: support@poily.com.