Help
FAQ
Common questions about PIILOT automations, agents, integrations, and safety.
Is PIILOT building pilots?
No. PIILOT builds automations and agents from natural-language workflow requests. The product focuses on automation creation, integration, validation, refinement, and controlled execution.
Does PIILOT run workflows automatically?
PIILOT generates and saves workflow drafts, compiles setup requirements, validates the graph, and supports run-preview and approval-oriented execution patterns. Users should review setup, validation, permissions, and approval gates before treating a workflow as live.
What is Composio used for?
Composio is used for integration discovery, managed authorization flows, connected-account identifiers, and executing supported third-party tool actions.
What does PIILOT store?
PIILOT stores account records, profile context, saved workflow JSON, integration connection metadata, notifications, approval state, rate-limit/session records, and operational diagnostics needed to provide the service. Browser local storage may also keep workflow drafts and selected workflow state.
Is PIILOT SOC 2 or ISO 27001 certified?
PIILOT is designed around SOC 2 and ISO 27001-aligned controls. That wording should not be interpreted as certification unless PIILOT separately publishes a completed audit report or certification statement.
Can external agents use PIILOT?
Yes. PIILOT exposes an MCP control plane for external MCP-capable clients. MCP clients use bearer tokens, scopes, status tracking, revocation, and recent tool-call records.