For the complete documentation index, see llms.txt. This page is also available as Markdown.

Sending Mail from Agentic Workflows with Postalytics

Overview

Agentic Workflows let you send Postalytics mail at scale in Kizen by triggering mail sends based on defined events and conditions. This allows you to include physical mail as part of repeatable Workflows without manual intervention.

Use Agentic Workflows when you want to:

  • Send mail automatically after a specific event or Record update

  • Trigger mail for many Contacts at once

  • Standardize and scale mail-based Workflows


Before You Begin

Before creating an Agentic Workflow that sends mail using Postalytics, make sure the following are in place:

  • The Postalytics integration is enabled in Kizen

  • A Postalytics campaign is created and available to select

  • Contacts included in the Agentic Workflow contain the required mailing fields:

    • First name

    • Last name

    • Street address

    • City

    • State

    • ZIP code

  • You have permission to create and edit Agentic Workflows

  • You understand when the Agentic Workflow should trigger and which Contacts it should apply to

Having these prerequisites in place ensures the Agentic Workflow can send mail successfully when it runs.


1

From your Top Navigation, go to Agentic Workflows

2

From the Agentic Workflow Builder, Select New Agentic Workflow

3

Enter your Agentic Workflow Name

4

In the Choose Agentic Workflow Object dropdown, choose Contacts

5

Select SAVE

6

In the Agentic Workflow Builder, add an Action

To add an Action, grab the Action button and drag it onto the Agentic Workflow Builder page or you can click the + then select Add Action from the menu.

7

In the Action Modal under Integrations, select Postalytics,

8

Next, Select Send Drip Campaign from the Action dropdown

9

From the Agentic Workflow Variable dropdown, choose the Campaign ID.

Under Script Inputs, configure the Campaign ID:

  • Set Input Source to Static Value

  • Leave Data Type set to String

  • In the Value field, paste your Postalytics Campaign Endpoint ID

Note: If you have not retrieved your Postalytics Campaign ID, see Locating your Campaign Endpoint ID in Postalytics.

10

All other required inputs from the Contact will be pre-populated

These are:

  • Last name

  • Street address

  • City

  • State

  • ZIP code

You only need to remap fields if you use non-standard Contact fields or want to map a different field.

11

Select SAVE

Your Agentic Workflow is now ready for the drip campaign you selected.


Testing Sends with Sandbox Mode

The Send Drip Campaign action also includes an optional Run in Sandbox Environment input. When set to Yes, the send is routed to Postalytics' sandbox environment instead of production, allowing you to validate Agentic Workflow logic and field mapping without generating real mail.

To enable sandbox mode on an Agentic Workflow:

1

Under Script Inputs, locate the Run in Sandbox Environment row

This row appears alongside the other Script Inputs.

2

Configure Run in Sandbox Environment values

  • Set Input Source to Static Value.

  • Leave Data Type set to Boolean.

  • In the Value dropdown, select Yes to route sends to sandbox. Leave the Value blank or select No for production sends.

3

In the Value dropdown, select Yes

To route sends to production instead, leave Value blank or select No.

Note: Because Run in Sandbox Environment is an optional input, it can be left unconfigured. If you do not set a value, the send defaults to production.

4

Select SAVE

Sandbox API Credentials

Sandbox sends require separate Postalytics API credentials from your production integration. These credentials are configured per user in your user settings. If you attempt a sandbox send without sandbox credentials configured, the Agentic Workflow step will fail with an authentication error.

Verifying Sandbox Sends

Sandbox sends do not produce physical mail. To confirm that a sandbox send was received by Postalytics, review the reports and activity logs in the Postalytics dashboard. For details, review Postalytics documentation.

Note: Sandbox mode is configured per Agentic Workflow. A single Agentic Workflow can include both sandbox and production sends if you need a staged rollout.


Agentic Workflow Runtime Behavior

Once a Postalytics Agentic Workflow is configured and saved, it runs automatically whenever its trigger conditions are met. No further user action is required.

When the Agentic Workflow runs:

  • Kizen validates required Contact mailing fields

  • Kizen sends the Contact data and campaign endpoint ID to Postalytics

  • Postalytics queues the mail for printing and delivery

Agentic Workflow sends are asynchronous. A successful run indicates the send request was accepted by Postalytics, not that the mail has been delivered.

Verifying and Monitoring Agentic Workflow Sends

You can monitor Agentic Workflow behavior in the following ways:

  • Agentic Workflow run history: Each execution appears in the Agentic Workflow’s run history. Successful runs indicate the send completed without errors.

  • Failure notifications: If a send fails, the run is marked Status: failed, and the Agentic Workflow owner receives an email notification with error details.

  • Postalytics dashboard: Delivery and mailing status are managed in Postalytics and are not tracked in Kizen.


Locating your Campaign Endpoint ID in Postalytics

To create an action for a Postalytics Agentic Workflow, Kizen needs to know which specific Postalytics campaign to trigger when the Agentic Workflow runs. In Kizen, this is called the Campaign endpoint ID.

1

In Postalytics, select Campaigns > View Campaigns

2

Select the ellipses to open the Campaign menu, then choose Settings

3

In Settings, copy the Campaign Endpoint

You should now have the Postalytics Campaign Endpoint ID. For more information on Postalytics Campaigns, visit the Postalytics Support Center.


What's Next

Next, review Sending Mail from a Contact Record with Postalytics to learn how to send one-time mail directly from individual Contact Records.

For broader context, you can also revisit the Postalytics Overview to understand available actions, common use cases, and error handling across the integration.

Last updated

Was this helpful?