Connect Dpd2 to Salesforce service cloud
When something happens in Dpd2, Notis takes the next step in Salesforce service cloud. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Dpd2 to Salesforce service cloud
Turn flagged emails into support cases
Send a Dpd2 email selected for support into Salesforce as a case, so customer requests do not get lost in the inbox.
Review unassigned cases each morning
Have Notis check Salesforce for unassigned cases on a schedule and surface the ones that need an owner.
Capture urgent customer emails as cases
Route an urgent Dpd2 message into Salesforce as a case so a high-priority request gets a durable follow-up record.
Find stale cases with inbox context
On a schedule, find aging open cases and check Dpd2 for relevant customer correspondence to inform follow-up.
Record repeat customer issues
Send a Dpd2 message identified as a repeat issue into Salesforce so the recurring problem has a case record.
Reconcile case status with recent email
Review open Salesforce cases on a schedule alongside recent Dpd2 conversations to find apparent follow-up gaps.
Capture refund requests for review
Create a Salesforce case when a Dpd2 message is selected as a refund request, keeping the decision and follow-up in view.
Get a manageable case backlog digest
Query Salesforce on a recurring schedule and turn the open-case backlog into a concise review with Dpd2 context.
Track billing questions in Salesforce
Create a Salesforce case from a Dpd2 billing question selected for support, so a response can be tracked to completion.
Supported Triggers and Actions
Notis builds workflows that link Dpd2 to Salesforce service cloud. A trigger fires from one place; an action lands in another.
Dpd2 triggers
Salesforce service cloud actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Agent Sensitive Data Rule Triggered
Notifies Salesforce Live Agent that sensitive data rules were triggered in agent messages. **Purpose**: When an agent's outgoing message contains sensitive data (SSN, credit card, email, etc.), call this action to apply configured masking or handling rules to protect customer privacy. **Prerequisites**: - Active Live Agent chat session with valid chat_id - Sensitive data rules configured in Salesforce Setup - Live Agent feature must be enabled in your Salesforce org **Note**: Salesforce Live Agent Chat is deprecated and retiring February 14, 2026. Migrate to Messaging for In-App and Web for continued support. **Typical Flow**: 1. Agent sends message containing sensitive data 2. System detects sensitive content matches a rule 3. Call this action with the chat_id and triggered rules 4. Salesforce applies masking/filtering per rule configuration
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Chasitor Sneak Peek
Send real-time typing indicator (sneak peek) to Live Agent during active chat session. Allows agents to see what visitors are typing before the message is sent. Requires an active Live Agent chat session with valid session_key and affinity token. The sequence number must increment with each request.
Composite Batch
Tool to execute multiple independent REST subrequests in one batch call. Use when bundling up to 25 independent operations to minimize round trips. Subrequests cannot reference each other.
Composite Request
Execute up to 25 dependent Salesforce REST subrequests in a single API call. Subrequests execute sequentially and can reference results from earlier requests using '@{referenceId.field}' syntax. Use this when operations depend on each other (e.g., create Account then create related Contact). For independent operations, use Composite Batch instead.
Composite SObject Tree
Create one or more nested sObject record trees in a single API call. Supports parent-child relationships up to 5 levels deep, with a maximum of 200 total records across all trees. Use this for bulk insertion of related records (e.g., Account with Contacts, or Orders with Line Items). Relationships must be Master-Detail or Lookup. Only supports INSERT operations, not upserts.
Create Case Record
Tool to create or upsert a Salesforce Case record. Use when you need to add a new Case or update via external ID.
Delete Case Record
Tool to delete a Salesforce Case record. Use when you need to remove a case by its record ID.
Describe SObject
Tool to retrieve metadata of any sObject. Use when you need to inspect field definitions, relationships, and supported features for objects like Account, Contact, Case, etc.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Dpd2 and Salesforce service cloud
Connect any two apps with Notis in the middle.
Dpd2 and Salesforce service cloud, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Salesforce service cloud.