Connecting TNZ with Keap

Overview

• TNZ's Keap (InfusionSoft) integration adds SMS Sending capabilities to Keap.
• The Keap contact must have a Mobile field and the Campaign must have a Message field.
• An HTTP success means TNZ accepted the request; it does not mean the SMS was delivered. Reporting and tracking occurs in the TNZ Dashboard.

Set up the integration

In the TNZ Dashboard:

1. Log into https://my.tnz.co.nz/
2. Under Users, click on your Username.
3. Toggle Enable API to On.
4. Enable the Sender/APIKey.
5. Save your Sender and APIKey values somewhere safe.

In Keap:

1. In the Keap campaign builder, add a Send HTTP Post action at the required point.
2. Set the URL to https://api.tnz.co.nz/api/v2.04/HttpApi/SMS.
3. Add a field named Sender and enter the dedicated TNZ Sender.
4. Add a field named Token and enter that User's TNZ APIKey.
5. Add a field named Number. Use Keap's Merge control to select the contact field that contains the mobile number. Do not copy a merge-field name from another Keap account without checking it.
6. Add a field named Message and enter the SMS text or the approved merge content.
7. Save the action. Keep the request as an HTTPS form POST and do not move credentials into the URL.
8. Run the campaign with a test contact, then inspect the TNZ delivery result.

Troubleshooting

The request returns 401

Check that Sender and Token contain the dedicated User's Sender and APIKey and that Sender/APIKey access is enabled.

The destination is blank

Open the Number field and select the correct contact mobile field through Keap's Merge control.

Keap reports success but no SMS arrives

Find the message TNZ reporting and review the delivery result.

The HTTP Post action is unavailable

Ask Keap Support whether your edition includes the legacy Send HTTP Post campaign action.

Related help

• TNZ SMS HTTP/S API documentation
• SMS delivery result codes