Where integrations fit
Start with the browser companion workflow first. Once the team workflow is validated, QuickLead Workspace can support structured delivery into CRM or internal systems through the private integration roadmap.
- Browser Companion first
- API and webhooks later
- CRM and internal delivery after beta validation
Later, not now
This is not a public self-serve developer platform yet. It exists to explain where integrations fit after the browser and workspace workflow is proven useful.
Planned integration capabilities
When integrations open up after beta, the goal is structured delivery into the systems teams already use.
- Structured JSON payloads
- Signed webhook delivery
- Idempotency keys
- Retry handling
- Delivery logs
- CRM and internal workflow delivery
- Tenant and workspace-aware usage
- Case-by-case rollout for validated teams
Current workflow
During beta, the supported workflow is Copy row / Export CSV. Google Sheets delivery or CRM delivery can be configured during pilot setup when appropriate.
- Browser Companion
- Real Estate Quick Extraction
- Real Estate Deep Extraction
- Workspace invites
- User-level attribution
- Pooled credits
- Copy row
- Export CSV
What comes later
Teams that validate the workflow can discuss structured delivery into CRM or internal systems later, once the browser-first path is worth formalising.
- Integrations are discussed case-by-case during the pilot
- No public SLA or public API packaging yet
- No broad self-serve integration program during beta
What not to expect yet
- No public production SLA yet
- No self-serve webhooks yet
- No guaranteed CRM connector list yet
- API and webhook pricing and packaging are not final
- Browser Companion remains the primary beta workflow
Talk to us about future integration
If your team wants structured delivery later, start with the QuickLead Estate workflow first. Once that flow is validated, QuickLead Workspace can scope the right next integration step with your team.
QuickLead Workspace integrations