CRM · potential integration
Salesforce
Approved account, opportunity and activity context can support sales workflows without granting unrestricted CRM access.
Potential connections
What the system may contribute
Use approved opportunity fields
Create reviewed activities and tasks
Route inbound enquiries
Example integration
Inbound enquiry to CRM
Enrich an enquiry with account context before an approved CRM action.
- inputInbound enquiry
- aiExtract requirements
- dataAccount lookup
- ruleBusiness rules
- humanSales approval
- outputActivity + follow-up
Example integration
Lead event routing
React to a CRM event and create the appropriate task.
- WebhookNew lead event
- integrationIntegration layer
- ruleQualification rules
- humanReview exception
- outputOwner + task
Access boundary
Authentication and permissions determine capability
Authentication
- OAuth
- Customer-approved connected application
- Scoped service identity
Access notes
- A workflow may only need to read account context and create an activity.
- Delete rights and unrelated CRM objects should remain outside scope.
Human control: Commercial commitments and high-impact record changes remain with authorised sales users.
Finch Island is not claiming a partnership, certification or completed client integration with this vendor. Implementation depends on supported APIs, licensing, authentication, permissions and the customer environment.
Project context
Describe the process and systems involved.
Finch can assess where AI, software, integration, rules and human control belong.