Documentation

Open App

Get Started

Quick Start

Create your first PIILOT automation from a manual workflow request.

  1. 1 Create an account from the registration page, accept the Privacy Policy and Terms of Service, and sign in.
  2. 2 Complete onboarding so PIILOT can personalize guidance around your role, company context, intended use, and technical comfort level.
  3. 3 Open Integrations and connect the tools the automation will need, such as Gmail, Google Sheets, Slack, HubSpot, Notion, Zendesk, or another supported toolkit.
  4. 4 Open Discovery and describe the manual workflow in plain language.
  5. 5 Review the generated workflow draft card, including risk level, recommended status, node count, branch count, connector count, validation result, and real need.
  6. 6 Save the workflow, then open it in Workflows or Canvas.
  7. 7 Review validation notes, setup requirements, approval gates, and connector mappings before treating it as runnable.
  8. 8 Refine the request or workflow until the automation matches the intended operating process.
First automation path
flowchart TD
  A[Register and accept legal terms] --> B[Complete onboarding]
  B --> C[Connect integrations]
  C --> D[Describe workflow in Discovery]
  D --> E[Review generated draft]
  E --> F{Validation clean?}
  F -- Yes --> G[Save and inspect in Canvas]
  F -- Needs review --> H[Refine prompt or configuration]
  H --> D
  G --> I[Configure auth, mappings, and approvals]
  I --> J[Run safely]

What to include in the first request

  • The trigger: what starts the automation.
  • The input source: email, form, spreadsheet, CRM, support ticket, message, or another system.
  • The decision rules: when branches should split.
  • The actions: what PIILOT should create, update, summarize, route, or notify.
  • The safety expectations: which actions require human approval.
  • The success metric: how the team will know the automation worked.
Review before running

PIILOT creates structured automation drafts and setup mappings. Users remain responsible for checking logic, permissions, approvals, and connected-app effects before running workflows against real systems.