Integrations · CRM & outcomes
Salesforce
On the roadmap, after HubSpot and Pipedrive prove the outcome loop.
- Method: Native
- Direction: Send and receive
- Availability: Later
On the list, built when beta users ask for it. Listing it here is not a commitment.
What it does
Lead or contact creation with approved mappings; opportunity-stage outcomes back. Scoped for self-serve customers, not a general sync engine.
What comes back
Mapped opportunity outcomes on linked records.
Not implied
That internal Salesforce experience equals a shipped self-serve connector.
Delivery is not an outcome
An accepted webhook, a posted Slack message, or a created CRM contact means the send succeeded. It does not mean anything downstream worked, and it certainly does not mean the inquiry became a customer. Formwink keeps receipt, human qualification, and recorded outcome as three separate facts.
Formwink is in beta.
Connectors ship in the order beta users ask for them.