Skip to main content
Dilli turns received email into activity inside the CRM. Each organization gets its own address; email that arrives there becomes an activity on the contact and its related deals. Auto-contact creation is opt-in: if you set nothing beyond the address, email is logged but no new contact is created.

​
Two entry paths

Ingestion has two entry points that end in the same place.
  • Native: each organization gets a {slug}@inbound.dilli.studio address. Email sent to it is delivered to the platform and processed. No provider setup required. This is the path described on this page.
  • Your own Resend: an organization already running its own Resend account points that webhook at an automation. See Inbound via Your Own Resend.
Both paths share the same matching, enrichment, contact-creation, and activity-logging behavior.

​
How the sender is identified

Sender resolution follows an order:
  1. By contact identity (email): if the sender address is already linked to a contact as an identity, the email lands on that contact.
  2. By contact email field: with no matching identity, the system looks up the email on the contact record.
  3. Auto-creation: with no contact found and the toggle on, a new contact is created with source email_inbound.
When the contact exists but is missing a name or email, those fields are filled from the received email.

​
Logging and idempotency

Each processed email becomes an activity of type email on the contact and its related deals. Ingestion is idempotent. Each email is logged once, identified by the combination of organization, provider, and the provider’s email ID. The same email redelivered does not create a duplicate activity.

​
Forwarding an existing email address

The most common path isn’t advertising the inbound address — it’s keeping the email you already use and forwarding a copy to Dilli. You keep using [email protected]. In your email provider, set up automatic forwarding to your {slug}@inbound.dilli.studio address. Each received message forwards a copy to Dilli and is ingested normally. For the sender and the original inbox, nothing changes.

​
Step by step in Gmail

Forwarding is set up in Gmail on desktop — not the mobile app. Open Gmail, click Settings, then “See all settings”. Then:
  1. Open the “Forwarding and POP/IMAP” tab.
  2. Under “Forwarding”, click “Add a forwarding address” and enter your organization’s {slug}@inbound.dilli.studio address.
  3. Gmail sends a verification message to that address. The code appears as an activity in Dilli — copy it from there.
  4. Return to Gmail settings, refresh the browser, and reopen the “Forwarding and POP/IMAP” tab.
  5. Select “Forward a copy of incoming mail to” and choose the Dilli address.
  6. Keep the recommended option to keep Gmail’s copy in the Inbox, and click “Save Changes”.
From then on, every email received in Gmail forwards a copy to Dilli and becomes a contact activity. To forward only some emails, create a Gmail filter and apply forwarding to messages that match the criteria.

​
Fields

​
Inbound address (default: auto-generated)

The organization’s {slug}@inbound.dilli.studio address. The slug is generated and filled automatically. Visible in Settings → CRM.

​
Auto-create contact (default: off)

When on, email from an unknown sender creates a new contact with source email_inbound. When off, email from an unknown sender is processed without creating a contact.

​
Automation events

Ingestion emits two events that can trigger automations:
  • email.received — whenever an email is ingested successfully.
  • email.contact.auto_created — when ingestion creates a new contact.
Use these events to chain follow-up, notification, or card movement.

​
Compatibility

If you configure nothing, nothing changes. The address exists, but without traffic there is no ingestion. Auto-contact creation starts off — you turn it on when you want.

​
Scope limits

Not a mailbox. Dilli does not store or display the inbox as an email client. Not sending. This feature covers only inbound email — outbound, campaigns, and email replies are not part of it. Not a real-time chat channel. Email becomes activity and history, not a chat thread.