Integrations and Add-Ons

Salesforce CRM

Vilulia's Salesforce integration provides bidirectional sync between Vilulia and your Salesforce org. Case parties (complainants and respondents) are synced to Salesforce as Contacts, and cases are synced as Opportunities. Vilulia checks for an existing Contact by email before creating a duplicate. There is one Salesforce connection per Vilulia organization.

What you'll learn

How to connect Salesforce to Vilulia
How parties and cases are synced to Salesforce objects
How conflict resolution works (last-write-wins)
How the circuit breaker handles API failures

Setup steps

Go to Settings → Integrations and click Connect Salesforce.
You are redirected to Salesforce. Sign in to your Salesforce org.
If you use a Salesforce sandbox, check the Use Salesforce Sandbox checkbox on the connect screen before the OAuth redirect. This checkbox is unchecked by default (connects to production). Checking it routes the OAuth flow to test.salesforce.com instead.
Salesforce asks you to authorize Vilulia. Vilulia requests api and refresh_token scopes. Click Allow.
You are returned to Vilulia. Your Salesforce organization ID and user details are saved.

What syncs automatically

Parties → Contacts: Case parties are synced to Salesforce as Contacts. Vilulia checks for an existing Contact by email address before creating a new one, to avoid duplicates.
Cases → Opportunities: Cases are synced to Salesforce as Opportunities.
Access tokens expire in approximately 2 hours; Vilulia refreshes them automatically.

Conflict resolution

When the same record is updated in both Vilulia and Salesforce between syncs, the last-write-wins approach is used — the most recent update takes precedence.

Circuit breaker behavior

The Salesforce integration uses the same circuit breaker pattern as QuickBooks: opens after 5 consecutive API failures, pauses requests for 60 seconds, then resets after 2 consecutive successes.

Can't find what you're looking for? Contact Support