These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
Integrations
Connect customer channels and business services with clear evidence and ownership.
The connections below are implementation options to configure and verify with the selected providers. Confirm the actual actions, identity boundaries and reconciliation rules before enabling a connection.
- Capture and customer context
- Forms and lead sourcesin and out
- Enrichment servicesin and out
- Email and calendarsin and out
- Campaign delivery
- Email and other campaign channelsContacts · in and out
- Delivery and engagement eventsin and out
- Offers and agreements
- Product and price sourcesProducts, Currencies, Configurations · in
- E-signaturein and out
- Fulfilment and provisioningin and out
- Finance and sales compensation
- Accounting and receivablesInvoices, Currencies · in and out
- Tax servicesin and out
- Payroll and payout providersin and out
- Reporting and identity
- Identity providersUsers · in and out
- Reporting platformsCurrencies · out
- Agents
- Your agentWorks within the permissions you assign
Capture and customer context
- Forms and lead sources. Retain the source identity, capture time and submitted fields. Resolve repeated events and possible duplicates before routing or conversion. New source data must not overwrite a reviewed customer identity without an explicit change policy.
- Enrichment services. Store the provider, observation date and field provenance. Review conflicts with known customer information. An enrichment response supplies evidence; it does not independently qualify a lead or authorize outreach.
- Email and calendars. Match messages and meetings to the appropriate user and customer context. Distinguish drafts, scheduled work and confirmed activity. Access and reporting follow the account/team boundary and the actual delivery or completion evidence.
Campaign delivery
- Email and other campaign channels. Select the supported providers and release policy for each channel. Resolve one recipient identity and recheck current preferences before sending. Merged or converted contacts retain suppression; a campaign membership record is not send authorization.
- Delivery and engagement events. Authenticate callbacks and attach them to the original message. Repeated opens, clicks or delivery updates do not create another send or award the same scoring signal again. An uncertain outcome stays unresolved until the provider evidence supports a safe retry.
Offers and agreements
- Product and price sources. Map effective products, configurations, prices, units and currencies into reviewed commercial versions. Changes to source data do not replace the prices or options on a customer-accepted agreement.
- E-signature. Bind the envelope, required signers and completed artifact to the exact approved version. A partial, voided or obsolete callback cannot activate a different contract. Retain failed and superseded attempts for reconciliation.
- Fulfilment and provisioning. Link confirmed external delivery to the accepted line and quantity. Keep partial completion and remaining scope explicit. A header status or outbound request alone does not prove the customer received the whole order.
Finance and sales compensation
- Accounting and receivables. Agree ownership of invoice issue, tax, cash and credit application, along with the accounting acceptance and revenue-recognition handoff. Preserve source IDs and currencies so a sync cannot create duplicate invoices or subtract payment history twice.
- Tax services. Retain the calculation inputs, response, applicable jurisdiction and rounding basis used before issue. Missing evidence remains an exception; a timeout does not establish a zero tax amount.
- Payroll and payout providers. Send only an independently authorized payout request against the approved commission statement, and retain the request identity. Acknowledgement, acceptance, rejection and confirmed payment are distinct outcomes. Paid status requires settlement evidence; unknown execution must be reconciled before another request can spend the same obligation.
Reporting and identity
- Identity providers. Map authenticated users to their roles, entity and team. Leaver and territory changes preserve historical customer ownership and commission attribution while removing current access as appropriate.
- Reporting platforms. Export defined commercial, forecast and receivables populations with dates and currencies. Apply commission privacy to exports and composite customer views as well as source records. Bookings, invoicing and recognized revenue need their own labels.
How connections are governed
service accounts, audit, pausingGive each connection a named owner and restricted service identity. Define source keys, content hashes, revision checks and destination-specific delivery history. Replays reuse existing effects; changed content under the same identity requires review. Monitor unresolved outcomes and reconciliation totals before widening access or enabling another automated action.
The API is one more client of the same interface. AI assistants and API →
# Example work after configuration
$ curl -s erp.ai/skill.md
› Summarize the open opportunities and latest commitments on my accounts.
› Prepare a qualification review from the lead's source and activity history.
› Explain which quote lines need commercial or technical review.
› Compare this forecast with its previous submitted version.
› Find renewal work affected by a changed or terminated contract.
› Explain a commission difference using the frozen plan and credited sales.
› Suggest a payment application without changing the original receipt.