Connect Salesforce to your other systems in a sentence.
Describe an integration in AI Command, or build it in Integration Studio. Runs are scheduled, webhook or event driven, safe to repeat, retried when they fail, and logged.
Available connectors.
Native two-way sync with Tripletex accounting. No middleware.
Tripletex ⇄ SalesforcePost Salesforce events, approvals and alerts to channels.
Salesforce → SlackBring payments, customers and invoices into Salesforce records.
Stripe → SalesforceScheduled batch extracts to Snowflake, BigQuery or Redshift. SOQL results are paged automatically.
Salesforce → WarehouseCall any HTTPS API with mapped fields. Requests to internal addresses are blocked.
Salesforce → Any APIA signed Nova webhook URL that turns incoming payloads into Salesforce records.
Any system → SalesforceSubscribe to Salesforce Platform Events live and forward them to other systems.
Salesforce → AnywhereTripletex and Salesforce, synced directly.
Nova connects to Tripletex directly. You no longer need an edge function in the middle. Your accounting data appears on Accounts, and new Salesforce records are created in Tripletex without duplicates.
- Tripletex → Salesforce. Customers, invoices, orders, projects, products and employees, matched on an external ID so reruns update instead of duplicating.
- Salesforce → Tripletex. Customers, products and projects. Rows that already have a Tripletex ID are updated; new ones are created and the new ID is written back to Salesforce.
- Ready-made Account mapping. Customers arrive with a default field map you can change.
- Tokens stay in the vault. Consumer and employee tokens are stored encrypted and exchanged for a session token on each run.
- Test first. The Tripletex test environment is the default. Production has to be switched on explicitly.
- Health check. Confirms which Tripletex company you're connected to.
Setup: the target object needs an External ID field (default Tripletex_Id__c). Tripletex webhooks are not supported yet. Syncs run on a schedule or on demand.
Three triggers, one run loop.
New integrations go through the same understand → plan → approve pipeline as any other change. They're created inactive, and the creation is logged.
SCHEDULE dispatcher checks every minute: what's due? ──┐
WEBHOOK outside system calls Nova (signature checked) ─┼──► QUEUE ──► already done? (idempotency key) ── yes ─► skip
EVENT a Salesforce Platform Event fires ────────────┘ │ no
▼
CONNECTOR does the work
│
success ◄───────────────┴──────────► failure
│ │
record the run retry with back-off
│ still failing
▼
dead-letter queue + incident on the
dashboard and in Org Brain's timeline
Safe to repeat
Idempotency keys make sure a retried run never writes the same record twice.
Encrypted secrets
Keys and tokens are entered in an encrypted vault. Pasting one into chat doesn't store it: it's removed before storage.
Internal addresses blocked
Outbound calls can't reach internal or private network addresses.
Picks up after a restart
Platform Event subscriptions remember the last event they processed, so a restart doesn't lose events.
Need a connector we don't have yet?
The connector framework is open to your team. Or ask us, and tell us which system you need.