> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-a-contact-record-with-postalytics.md).

# Sending Mail from a Contact Record with Postalytics

{% hint style="success" %}
**Audience:** Admins, Developers, <code class="expression">space.vars.automation</code> Builders, Support & Operation teams, and Solution Architects

**Purpose:** Explains how to send one-time mail from a Contact record in <code class="expression">space.vars.Kizen\_company\_name</code> using the Postalytics integration.
{% endhint %}

## Overview

{% hint style="warning" %}
**Caution:** This setup reflects <code class="expression">space.vars.Kizen\_company\_name</code>'s default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
{% endhint %}

Sending mail from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> is useful for one-time mail sends, such as individual outreach or ad hoc follow-ups using [Postalytics](/docs/integrations-and-plugins/integrations/postalytics.md).

To send mail successfully, the <code class="expression">space.vars.contact</code> must include a first name, last name, street address, city, state, and ZIP code. If any required fields are missing, the send will fail and a toast message will list all missing fields so they can be corrected before retrying.

***

## Before You Begin <a href="#when-to-use-postalytics" id="when-to-use-postalytics"></a>

Before sending mail from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> using Postalytics, make sure the following are in place:

* The [Postalytics integration](/docs/integrations-and-plugins/integrations/postalytics/enabling-postalytics.md) is enabled in Kizen
* You have access to the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> you want to send mail from
* The <code class="expression">space.vars.contact</code> includes the required mailing fields:
  * First name
  * Last name
  * Street address
  * City
  * State
  * ZIP code

If any required fields are missing, the send will fail and a toast message will list all missing fields so they can be corrected before retrying.

***

{% stepper %}
{% step %}

#### Navigate to **Data** > **Contacts**

{% endstep %}

{% step %}

#### Open a Contact Record

{% endstep %}

{% step %}

#### Select Perform Action

<div data-with-frame="true"><figure><img src="/files/GXW1LNeiBnunJWyeG8dk" alt="" width="320"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

#### Choose Send Campaign Mail

{% endstep %}

{% step %}

#### From the Select Campaign Modal, select the drip campaign you want mailed out.

{% endstep %}

{% step %}

#### Confirm Send

{% hint style="info" %}
**Note**: Only Triggered Drip campaigns are supported. Bulk mailer campaigns are not available through the <code class="expression">space.vars.Kizen\_company\_name</code> integration currently.
{% endhint %}
{% endstep %}
{% endstepper %}

<code class="expression">space.vars.Kizen\_company\_name</code> sends the <code class="expression">space.vars.contact</code>’s data to Postalytics, which queues the mail for printing and delivery, and then displays a success or failure message in <code class="expression">space.vars.Kizen\_company\_name</code>.

{% columns %}
{% column %}
![check mark button](https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/standard/ef8b0642-7523-4e13-9fd3-01b65648acf6/32x32/2705.png) **Success feedback**&#x20;

* A toast notification confirms the mail was queued successfully
  {% endcolumn %}

{% column %}
![cross mark](https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/standard/ef8b0642-7523-4e13-9fd3-01b65648acf6/32x32/274c.png) **Failure feedback**

* Missing required fields are listed as error messages
* Authentication or API errors surface as error messages
  {% endcolumn %}
  {% endcolumns %}

***

## **What's Next** <a href="#sending-mail-from-automations" id="sending-mail-from-automations"></a>

Next, continue to [Sending Mail from Agentic Workflows with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-automations-with-postalytics.md) to learn how to trigger mail sends automatically as part of scalable, repeatable workflows.

<details>

<summary>Related Topics</summary>

* [Postalytics](/docs/integrations-and-plugins/integrations/postalytics.md)
* [Enabling Postalytics](/docs/integrations-and-plugins/integrations/postalytics/enabling-postalytics.md)
* [Sending Mail from Automations with Postalytics](/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-automations-with-postalytics.md)
* [Postalytics Troubleshooting & Error Handling](/docs/integrations-and-plugins/integrations/postalytics/postalytics-troubleshooting-and-error-handling.md)

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.kizen.com/docs/integrations-and-plugins/integrations/postalytics/sending-mail-from-a-contact-record-with-postalytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.