Skip to main content
A delegation is a standing job you hand to Klipy: watch for a trigger, like a new email or a meeting starting, and act on it without you asking each time. Klipy ships six ready-made delegations, plus custom ones you build yourself. Every delegation that would send something on your behalf always waits for your approval first.

​
What a delegation is

A delegation is not a one-off request—it is a rule Klipy keeps running for you. You set it up once, and Klipy watches for the trigger you defined (an email arriving, a meeting about to start, the first minutes of your day) and carries out the job every time that trigger fires, without you having to remember or ask again. You manage every delegation from one place: app.klipy.ai/delegation. Each delegation shows a status badge:
  • Enabled (green) — the delegation is connected and running.
  • Needs Configuration (coral) — the delegation is missing something it needs, most often a connected email or social account, or an output language.
  • Disabled (gray) — you turned the delegation off, or Klipy has not connected the accounts it depends on yet.
Klipy has two kinds of delegations. System delegations are six built-in jobs that cover the recurring work of running a sales pipeline alone—logging emails and messages, taking meeting notes, drafting replies, prepping for calls, and summarizing your day. Custom delegations are ones you write yourself: you choose the trigger and describe, in plain language, what you want Klipy to do. Turning a delegation on does not hand Klipy the keys to your inbox. A delegation that only reads and organizes information (like logging an email to a contact’s record) runs on its own, because it never leaves your workspace. A delegation that would produce something to send—an email, a reply on LinkedIn or WhatsApp—always stops and shows you a draft first. Nothing goes out under your name without you approving it.

​
The 6 built-in delegations

Klipy’s six system delegations cover email, messaging, meetings, and your daily pipeline view. Each one has its own page under app.klipy.ai/delegation where you can turn it on, check its status, or adjust its settings. Triage & log emails, Triage & log messages, and Take meeting notes only touch your CRM records—capturing and organizing what already happened—so they run without asking for your sign-off each time. Prepare email drafts always produces a draft that waits in your inbox until you approve it; Klipy never sends it on its own. Once you turn on the daily brief at app.klipy.ai/delegation/daily-brief, Klipy sends it by email (and shows it in-app) at the time you set—8am on weekdays by default. You don’t have to wait for the schedule: the “Send me one now” button on that page sends an on-demand copy immediately.

​
How approval works

The rule behind every delegation is the same: Klipy never sends anything on your behalf without you approving it first. This applies everywhere, including delegations that otherwise run in the background. A delegation like Triage & log emails or Take meeting notes never sends a message—it only reads, organizes, and logs information inside your own workspace, so it runs continuously without stopping for a click. A delegation like Prepare email drafts is different: it produces something that would go out to another person, so it always leaves a draft rather than sending it. You see every draft in your inbox exactly as Klipy would send it, and you can edit it, send it, or discard it. Klipy is never allowed to send an email or a message on a delegation’s behalf without that approval step. Custom delegations follow the same principle from the other direction. Because a custom delegation’s instructions are written by you and can cover more ground than a system delegation, Klipy shows you what it is about to do in a consultation view before it acts, so you can approve, adjust, or reject the action before Klipy carries it out.

​
Create a custom delegation

If none of the six built-in delegations match what you need, you can write your own. A custom delegation still follows the same approval rule as every other delegation in Klipy: it never sends anything without you signing off first.
1

Open the delegation builder

Go to app.klipy.ai/delegation/new.
2

Choose a trigger

Pick how the delegation should start: an event trigger fires when a specific CRM record or contact changes (for example, a deal moving to a new stage), and a cron trigger fires on a schedule you set (for example, every Monday morning).
3

Write the instruction

Describe what you want Klipy to do in plain language—there is no code or configuration syntax to learn.
4

Save the delegation

Klipy runs the delegation whenever the trigger fires. Each run is logged with a status—pending, success, failed, or approval-pending—so you can see what happened.
5

Review before anything goes out

Whenever a run would send a message or make a change worth confirming, Klipy shows it to you in a consultation view first. Nothing happens until you approve it.

​
When to contact us

Most delegation issues come down to a missing connection rather than a bug. If a delegation stays on Needs Configuration after you have connected the account it depends on, double-check which account it needs: Triage & log emails, Prepare email drafts, Take meeting notes, Prep before meetings, and Daily brief all need at least one connected email account; Triage & log messages needs a connected LinkedIn, WhatsApp, or Telegram account; Prepare email drafts also needs an output language set. If a delegation shows Disabled and you did not turn it off yourself, it may be waiting on one of those same connections. Reconnecting the account it depends on, or setting the missing language, should move it back to Enabled without needing to recreate the delegation. For a custom delegation that never seems to trigger, check that the trigger you chose actually matches what you expect—an event trigger only fires on the record type and change you specified, and a cron trigger only fires on the schedule you set. If you have checked your connections and a delegation still will not run, or a run’s status stays stuck on pending or failed with no clear reason, reach out through the Get help option in Klipy’s Help menu. A member of the team can look at the specific delegation and run history with you.
No. Klipy never sends an email, a LinkedIn message, a WhatsApp message, or a Telegram message on your behalf without you approving that exact draft first. Delegations that only log or organize information (like Triage & log emails) run automatically because they never leave your own workspace, but nothing Klipy would send goes out without your sign-off.
Klipy stops running that delegation the moment you disable it. It will not react to its trigger again—no new emails logged, no new drafts prepared, no new meeting notes taken—until you turn the delegation back on from its page under app.klipy.ai/delegation.
No. A custom delegation is built from a trigger you pick (an event on a CRM record, or a schedule) and an instruction you write in plain language. Klipy interprets the instruction; there is no script or configuration file involved.
Yes. Once you enable the daily brief at app.klipy.ai/delegation/daily-brief, Klipy emails it to you at your set time each weekday (8am by default), and it also appears in-app. Use the “Send me one now” button on that page any time you want an immediate copy instead of waiting for the schedule.
Yes. Each delegation, system or custom, keeps a run history with a status for every time it fired—pending, success, failed, or approval-pending—so you can confirm what Klipy did and when.
Last modified on August 3, 2026