Your company.
Connected to your tools.
Website leads land in the CRM with their source intact. A signed quote, a paid invoice or a system status change reaches your other tools as it happens. REST API access and signed webhooks are included with Powerlily Pro.
Posted once.
Never re-keyed.
Post the lead once, with its source and your own ID. Powerlily alerts the team, routes it when a form is linked, and a repeat delivery never makes a second lead.
- Your website or CRMThe inquiry comes in.
- Powerlily APIValidate the lead and create it once.
- Your CRM in PowerlilyThe lead lands with its source attached.
/api/v1/leads{
"lead": {
"name": "Avery Chen",
"email": "avery@example.com",
"external_provider": "your-crm",
"external_id": "lead-4242"
}
}
A create-only credential accepts new leads and nothing else. It cannot read, edit or delete the rest of your pipeline.
Read the integration brief ↗Leads in. Records in sync. Events out.
Pick the handoff that costs your team the most time. Each integration gets a named credential with only the scopes it needs.
- 01
Capture the lead
Post leads from your website, your ad platform or another CRM. The source and custom form answers stay on the record, and a linked form routes the lead to its owner.
CRM & lead capture ↗ - 02
Read and update the record
Read customers, projects, invoices, installed systems and your catalog from your own tools. Create or update leads, projects, tasks, events and schedule blocks where the specification allows it.
- 03
Hear about it as it happens
A quote is signed, an invoice is paid, a system changes status: each event reaches your endpoint signed and timestamped. Delivery history, retries and manual replay are built in.
For developers and coding assistants
Start with the actual contract.
Download the OpenAPI specification and the integration brief before you sign up. They list every supported endpoint, scope, request field and webhook check, so your developer builds against the interface that is live today.
Paste the same brief into an AI coding assistant and it has the contract, the signature steps and the field rules in one file. For an assistant that answers questions about your projects and daily work, MCP is the separate, read-only route.
- Scoped access
- Create a named credential for each integration. Pick its scopes, set an expiry and revoke it the day the connection ends.
- Predictable requests
- Documented JSON envelopes, pagination and change filters. An Idempotency-Key header makes a retried POST safe for 24 hours.
- Traceable events
- Every delivery carries a timestamped HMAC signature and its own attempt history. Replay a failed delivery once your receiver is back.
- Defined boundaries
- Invoices and payments are readable. Taking payment, signing and editing design geometry stay inside Powerlily. The specification lists every supported write.
Before you move anything
Keep your website. Connect the handoff.
Bring the tools you run today and the handoff you most want gone. In a demo we map it to the supported records and pick the credential scope it needs.
Guided onboarding is included on every plan. API access and webhooks are part of Pro, alongside weekly training and a dedicated account manager.
Ask us about your integration ↗Bring existing records with you
Import leads and customers from CSV. Connect Google Drive and pull the files you choose into the company library or onto the right project, lead or customer.
Keep your existing website
Embed a Powerlily lead form in the site you have, or connect the form that is already there. Moving the whole website is optional.
Website options ↗Connect the team’s calendar
Google Calendar sync flags private free/busy conflicts while you schedule. Each crew’s calendar feed opens in any calendar app.
Crew scheduling ↗Prove one connection first
Map the fields, issue the narrowest scope that does the job and watch the first lead or event land before you widen anything.
Bring your tools. We’ll map the handoff.
Show us the systems you keep and the data you re-type between them. We’ll show you the endpoint, the scope and the webhook that replace it.