Workspace-scoped OAuth
Connection and refresh handling use encrypted connector secrets; normal management responses do not expose the tokens.
Integration directory
Pipedrive integration
Bring approved Queast context into Pipedrive—with the contract visible
Pipedrive is listed as a supported OAuth connector in the current Queast product. Access is enabled per workspace, while public plan availability and the exact object, field, direction, and mapping contract must be confirmed before implementation.
Current connector status
Separate product support from universal availability
The current product catalog marks Pipedrive as supported. That does not make every workspace, plan, market, direction, object, field, or mapping automatically available.
- VerifiedConnector catalog
- Supported in the current product UI.
- VerifiedWorkspace access
- Integrations must be enabled for the workspace.
- VerifiedConnection setup
- OAuth is initiated by a workspace administrator and requires configured Pipedrive app credentials.
- ConfirmPublic plan and market
- Not approved for publication; confirm with Queast.
- ConfirmMarketplace or partnership
- Not established by the available evidence and not claimed.
Verified technical footing
Start from the connector controls that exist
The current implementation establishes a bounded connector foundation. The exact customer contract still depends on approved workspace configuration.
Outbound event handlers
Current delivery code recognizes company, person, and published Signal event families.
Connector identity mappings
Mappings preserve the relationship between a Queast record and its Pipedrive partner record for later delivery.
Delivery state
Idempotent jobs and attempts record status, retry scheduling, connector throttling, and optional write-budget state without promising a public SLA.
Verified footing is not a blanket promise. Production scope still depends on the approved workspace configuration.
Outbound object contract
Name the technical path without promising a universal mapping
The current handlers establish these destination roles. Exact fields, creation or update behavior, included artifacts, permissions, and customer availability remain configuration-dependent.
01CRM record
Organization
A company event can find, create, or update a supported Pipedrive organization and retain its connector mapping.
02CRM record
Person
A permitted person event can search by exact work email, create or update a supported record, and attach it to a mapped organization where available.
03CRM context
Activity and Signal note
A published Signal delivery has technical paths for a follow-up activity and a context note linked to the mapped organization.
04Human-reviewed draft
Optional proposed-message note
A proposed-message artifact can be transported as a note only when the approved export instruction includes it; it remains a draft for human review.
Movement contract
Describe each direction at its verified status
Do not summarize the connector as bidirectional sync. Outbound delivery and inbound interest have different events, identity rules, permissions, and launch states.
Implemented foundationOutbound
Outbound foundation
Current handlers recognize company, person, and published Signal events. Exact export profiles, destination fields, included artifacts, and availability remain configuration-dependent.
Explicitly included onlyDraft transport
Human-reviewed message artifact
A proposed-message note is optional and must be explicitly included. Transport does not approve, schedule, or send the message.
Launch unconfirmedInbound
Inbound interest
A configured organization label or custom-field change can become a Queast bookmark when identity resolves. Public launch is not confirmed.
Human controlDecision
Human workflow
Administrators approve connection scope and mappings; sellers review the delivered context and decide the next CRM action.
Identity before delivery
Keep mapped and unresolved records distinct
The current connector records connection-specific identities for organizations, people, notes, and activities. Exact organization matching and review policy still require implementation approval.
Explore company intelligence-
01
Organization candidate
Current outbound behavior can search by organization name before creating a record; the final matching policy is configuration-dependent.
-
02
Person candidate
Current person handling requires permitted work email and uses exact-email search before creation or update.
-
03
Approved mapping
The stored connector mapping associates the Queast subject with the Pipedrive partner record for scoped updates and attached context.
-
04
Unresolved inbound identity
The configured interest path can quarantine an event when the Pipedrive organization is not mapped instead of silently attaching it.
Implementation checklist
Confirm the contract before connecting
These are required implementation decisions, not claims that every Pipedrive connection exposes the same behavior.
Read Tech and Security- 1
Availability
Which plan, workspace, and market can use the connector?
- 2
Direction
Which outbound and inbound paths are enabled?
- 3
Objects and fields
What may be created, updated, associated, appended, or provisioned?
- 4
Identity and contact data
Which matching policy, permissions, allowlists, and review behavior apply?
- 5
Permissions
Which Pipedrive app scopes and Queast roles are required?
- 6
Operations
What delivery status, retry behavior, throttling, write budgets, limits, support, and audit detail apply?
Next step
Verify your Pipedrive contract with Queast
Confirm availability, direction, objects, fields, identity handling, contact-data policy, permissions, and operational scope before implementation.