CRM context
Keep selected account or person context connected to a supported CRM surface, within the connector's approved direction and field scope.
Platform overview
Integration directory
Choose the connection that fits your workflow
Keep Queast as the intelligence and preparation layer while selected context moves through an approved connection. Availability, direction, supported objects, and destination behavior depend on the connection and its approved configuration.
Connection directory
Start with the workflow, then verify the scope
Each entry explains an intended connection role. Its review status is a publication boundary, not a promise of live availability or a complete contract.
Scope to confirm
HubSpot
Review the proposed CRM connection for selected company, person, and Queast context. Confirm availability, movement direction, supported objects and fields, and identity handling.
Review scope
Scope to confirm
Pipedrive
Review the proposed CRM connection for selected organizations, people, and Queast context. Confirm availability, movement direction, supported objects and fields, and identity handling.
Review scope
Notification scope to confirm
Slack
Review Slack as a destination for supported Queast notifications. Confirm notification types, destinations, linking behavior, and administrative controls.
Review scope
Event contract to confirm
Webhooks
Review custom delivery for supported Queast events. Publish only the event catalog, payload contract, authentication, retry, and observability behavior proven in production.
Review scope
Scope-gated
MCP
Review MCP as a scope-gated integration direction. Customer gateway, client, tool, permission, hosting, and availability contracts remain unverified until approved.
Review scopeBrand assets identify directory entries only. They do not establish live availability, a partner relationship, or an approved connector scope.
Choose by workflow role
Connect context without changing its authority
The destination and contract change. The distinction between evidence, analysis, Composite Intents, recommendations, and human action does not.
Team notifications
Make supported Queast notifications available for review without implying that Slack is a conversational bot or action system.
Custom delivery
Carry an approved event contract into an internal workflow without reproducing Queast analysis or granting unrestricted data access.
Approved AI-client access
Expose only a bounded, permissioned tool catalog; do not treat MCP as open database or action access.
Human-controlled handoff
Keep authority visible across the connection boundary
A connection moves an approved artifact into a defined destination. It does not create evidence, issue a recommendation, or complete the human action.
-
01
Review Queast context
A person reviews the source evidence, analysis, preparation, or supported recommendation before it leaves the Platform.
-
02
Confirm the connection scope
Availability, direction, objects, fields, destinations, permissions, and secrets must match the approved configuration.
-
03
Deliver the approved artifact
The connection transports selected context; it does not recompute Composite Intents, bypass Actionable Signal eligibility, or invent missing evidence.
-
04
Continue with human judgment
A person resolves ambiguous identity, reviews notification or draft context, and decides the next action. Messaging is not autonomous sending.
Implementation checklist
Resolve the contract before connecting
Use these questions to evaluate the selected connection. They are review requirements, not claims that every connector exposes the same controls.
Availability
Is the connection available for this customer and market?
Direction
Is movement inbound, outbound, or both—and which direction is actually supported?
Approved scope
Which records, fields, notifications, events, or tools are in the production contract?
Identity and access
How are identity conflicts, permissions, and secrets handled and reviewed?
Delivery state
Which failure, retry, health, and audit details are available in the approved implementation?
Artifact authority
Is the payload source evidence, analysis, a Composite Intent, an Actionable Signal, SPICED preparation, or a human-reviewed draft?
Next step
Choose the connection, then verify the contract
Explore the relevant integration page for its intended role. Confirm the live availability, direction, and supported scope with Queast before implementation.