Integrate ZAP~POST with Omnisend

Connect Omnisend with ZAP~POST to send physical postcards to new contacts in supported countries. The integration checks Omnisend every 30 minutes and submits eligible contact and address information to the ZAP~POST campaign that matches the contact’s country.

This is a one-way integration from Omnisend to ZAP~POST. Delivery, return, and other ZAP~POST statuses are not synced back to Omnisend.

Make sure you have:

For example, you can name campaigns:

Step1. Sign in to the ZAP~POST ZAPP.

Step 2. Go to Settings → API Consumers. Select Add New Consumer.

Step 3. Select Generate New Keys.

Step 4. Copy the generated API Key and API Password.

You need both credentials to connect ZAP~POST to Omnisend.

Step 1. Open the ZAP~POST integration in the Omnisend App Market.

Step 2. Enter your ZAP~POST API Key and then your ZAP~POST API Password.

Step 3. Save the connection.

The integration uses these credentials to submit individual contact records to ZAP~POST.

The integration uses one Automation Workflow called Welcome Postcard.

The integration checks the selected campaign names and routes each contact to the campaign that matches their country.

The Campaigns field supports multiple selections. Select every ZAP~POST campaign that this Automation Workflow should be able to use.

The integration does not send each contact to every selected campaign. It compares the contact’s country with the name of each selected campaign.

For example:

ZAP~POST does not provide a separate country field for this routing. The campaign name is the country signal available to the integration.

Use clear campaign names, such as:

A contact from the United Kingdom or Northern Ireland does not route to a United States campaign, even when both campaigns are selected. These countries use different physical mail formats and require separate campaign setups.

Archived campaigns may remain visible in the campaign selector. They are labeled with the status provided by ZAP~POST and are excluded from receiving mail.

The integration routes a contact when their country matches a selected ZAP~POST campaign name.

The following countries have confirmed end-to-end support:

The routing logic can also match other countries when a correctly named campaign exists. Support for additional countries must be confirmed with an end-to-end test before you rely on it for production mailings.

ZAP~POST may support delivery to countries such as Germany, the Netherlands, France, and Italy. However, availability through this integration depends on having a matching campaign configured and tested.

The Submit Individual Record action sends contact data to ZAP~POST.

ZAP~POST requires enough name and address information to deliver the postcard. Contacts without sufficient information may fail validation or may not be deliverable.

Use Custom Data to send campaign-specific values that are not part of the standard contact fields.

Examples include:

These fields must already be configured for the campaign in ZAP~POST. Use the lowercase field name as the JSON key.

The action includes an Only Valid Records toggle.

When the setting is on, ZAP~POST rejects the entire submission if any field fails validation.

When the setting is off, which is the default, valid fields are submitted and validation failures are returned in the response.

Choose the setting based on whether you want one invalid field to block the entire submission.

The integration checks Omnisend for new contacts every 30 minutes.

ZAPPOST may internally combine individual submissions into one daily batch. This affects how records appear on ZAPPOST’s processing or reporting page. It does not change the mailing behavior.

A submitted record’s mail status may not be available for querying until the day after submission.

For a new or reconnected ZAP~POST account, this message can indicate an expired trial period.

Check your ZAP~POST trial or billing status before troubleshooting the Omnisend connection.

Confirm that the selected ZAP~POST campaign has published Front and Back artwork.

An unpublished campaign can return a 404 Not Found response. Omnisend cannot detect unpublished artwork before the submission.

Check the following:

When can I view the mail status?

ZAP~POST does not make the status of a submitted record available for querying on the same day. Check the status on the following day.

Does the integration sync ZAP~POST delivery statuses to Omnisend?

No. The integration sends contact data from Omnisend to ZAPPOST. It does not sync delivery, return, or other ZAPPOST events back to Omnisend.

How quickly does ZAP~POST send a postcard?

Omnisend checks for new contacts every 30 minutes. ZAP~POST may batch individual submissions internally for daily processing. The batch process affects reporting, not the integration’s sending behavior.

Can I use one campaign for multiple countries?

Use separate campaigns when countries require different physical mail formats.

The United Kingdom and Northern Ireland can use one shared campaign. The United States requires a separate campaign.

What should I do if a country does not receive mail?

Make sure a selected ZAP~POST campaign includes the contact’s country or recognized abbreviation in its name. Also confirm that the campaign is active and has published artwork.

If the issue continues, contact Omnisend Support with the Contact ID and ZAP~POST campaign name.