Quickstart

This section walks through a minimal setup: turning information into a monthly email report for a client. Before DelegateZero, I had a Pipedream workflow that looked something like this (simplified a bit):

1. Pull website analytics data for client
2. Analyze and create email text
3. Save in my email draft folder
4. Notify me in Slack that the email draft is ready

Then I would be responsible for reviewing the email draft, updating it based on what I knew to be true about the client and the client's accounts, and then send manually. I did it this way because, like everyone, I didn't trust AI to put together and send an email without my intervention.

Now, with DZ, the workflow looks similar but I'm confident that the email being created is accurate and comparative to something I would actually send. So I let it go ahead and send the email.

1. Pull analytics data for client
2. Analyze analytics data
3. Create email text (DelegateZero's step)
4. Send email to client

Let's zoom in on each step.

Step 1: Identify a decision that needs to be made

Start with a real decision you already make frequently that you'd like to have DZ handle for you going forward. For example:

• Approving small expenses
• Responding to routine internal requests
• Deciding whether something needs escalation

For my sample workflow, that was verifying the accuracy and legitimacy of the client email. When you're first getting started, I would recommend avoiding high-risk or irreversible decisions until you get more comfortable.

Step 2: Create or add DelegateZero to an existing workflow

After identifying where a decision needs to be made, create a step and send a request to DZ. For my workflow, I needed DZ at the create email step. Here is what that request looked like:

          curl -X POST https://delegatezero.com/api/v1/decisions \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "request": "Create a monthly website analytics report for a client.",
    "context": {
      "entity": "ABC Company",
      "data": "[This would be a paste of the analysis data.]"
    },
    "instructions": {
      "confidence_threshold": 0.8,
      "format": "html"
    }
  }'

          import axios from "axios";

const decision = await axios.post(
  "https://delegatezero.com/api/v1/decisions",
  {
    request: "Create a monthly website analytics report for a client.",
    context: {
      entity: "ABC Company",
      data: "[This would be a paste of the analysis data.]",
    },
    instructions: {
      confidence_threshold: 0.8
      format: 'html'
    }
  },
  {
    headers: {
      Authorization: `Bearer ${process.env.API_KEY}`
    }
  }
);

console.log(decision.data);

          import requests
import os

response = requests.post(
  "https://delegatezero.com/api/v1/decisions",
  headers={
    "Authorization": "Bearer {os.environ['API_KEY']}",
    "Content-Type": "application/json"
  },
  json={
    "request": "Create a monthly website analytics report for a client.",
    "context": {
      "entity": "ABC Company",
      "data": "[This would be a paste of the analysis data.]",
    },
    "instructions": {
      "confidence_threshold": 0.8
      "format": "html"
    }
  }
)

print(response.json())

Other than the API key and the delegatezero.com URL, the only required field is the request field.

Including more information may be helpful or even necessary for better responses. Adding context helps to improve accuracy. Instructions allow you to overwrite default behavior set in your account for specific requests.

Learn more about

Step 3: Receive the outcome

DelegateZero returns a structured outcome. In this example, the decision is safe to execute, so DZ proceeds and includes a short explanation and an audit link.

{
  "id": "9f31c2",
  "decision": "execute",
  "confidence": 0.86,
  "reason": "Email content aligns with the provided analytics data and prior client report templates",
  "response": "<p>Hi there,</p><p>Here’s your monthly website analytics report for January.</p><p>Overall traffic increased by 12% month-over-month, driven primarily by organic search. Conversion rate remained steady at 2.4%, with top-performing pages being /pricing and /blog.</p><p>Notably, paid spend decreased by 8% while total leads increased by 5%.</p><p>Let me know if you’d like a deeper breakdown or have any questions.</p><p>Best,<br />Your Team</p>",
  "audit_url": "https://delegatezero.com/app/decisions/9f31c2"
}

As you can see, the HTML string for the email was generated and the reasoning that DZ used to create the response was documented. With the audit URL provided (or accessed via your user dashboard), you can deep-dive into the decision to learn about how it was made and what you could add to improve the response.

Step 4: Review the audit log

In your DZ account, you can review past decisions and responses, including:

• What context was used (information, templates, entity data)
• Which rules applied ("if this client, do that")
• Why the outcome occurred (i.e. not enough data)
• The confidence level at the time of the decision

Performing regular audits of the decisions made in your DZ account and then making context improvements as outlined below will ensure accurate delegation and improved, efficient automated workflows.

Step 5: Improve with context

After reviewing past decisions, you can improve future outcomes by adding quality context. Some optimizations you can make include:

• Adding rules: alter responses based on platforms, data, people, etc.
• Add an example of a similar decision
• Add guidance for edge cases

Next steps

Great - so if you've followed along and added DelegateZero to one of your workflows, you're already on your way to a higher level of automation and a more efficient day-to-day. To get the most out of DZ, we recommend that you continue reading through the documentation below, particularly these sections:

1. Context: the different types of context and adding new context
2. Requests: how to submit decision requests
3. Settings: global settings, confidence thresholds, and safety