dialit.ai
Log inJoin Academy

Integrations

Plan authorized connections and verify the actions your agent can take.

Connect only what your workflow needs.

Voice runtime

Cartesia is the selected runtime path in this project. Actual voice, language and model compatibility must be confirmed for the deployed agent. A provider name is not a promise of every capability.

Calendar & booking

Calendar connections require authorization, availability checks, timezone handling and a controlled booking test. Until verified, capture a request for a human to confirm.

CRM & custom APIs

Agree the destination, allowed actions and fields. Use scoped credentials, deduplicate writes and make failures visible. Custom integration work is separately scoped.

Before an integration goes live

  1. AuthorizeConfirm ownership and the minimum data access.
  2. MapAgree fields, actions and failure handling.
  3. TestVerify controlled success, rejection and duplicate delivery.
  4. ActivateApprove production scope and an escalation owner.

WhatsApp, payments and other third-party actions have separate provider eligibility, consent and charges. Payment checkout for Dialit setup is not an agent payment-collection integration.

Discuss an integration →

Cookie settings

Essential storage supports account access, checkout recovery and your preferences. Optional site analytics stays off unless you allow it. Payment providers and the workspace have their own privacy notices.