You can optionally use SMS messaging in Automations, for example, automatically send a welcome SMS when creating a new Contact.
At the time of writing, Pipedrive only allows their own apps in Workflows. Alternative options include:
You can send SMS, Email and Voice broadcasts to your contacts.
In Pipedrive:
- Select Contacts
- Filter to display your chosen contacts
- Click '…' and click 'Export filter results...'
- Click 'Export' and select 'CSV'
- Download the CSV to your PC
In the TNZ Dashboard:
- Follow the appropriate guide for your message type:
SMS Broadcasts
Email Broadcasts
Voice Broadcasts
- When Selecting Contacts, import your Pipedrive CSV list
Troubleshooting and FAQ
Can I see my other TNZ SMS activities in Pipedrive?
Yes, any SMS messages sent using TNZ (e.g. the TNZ Dashboard, API, integrations) can display in Pipedrive as an Activity.
The Pipedrive user must have the 'Account Settings' option enabled to view activities that are not tied to their user.
This is configured under Settings, then Manage Users.
Alternatively, you can add these granular rights to a specific group of users:
I have multiple Pipedrive users. Do I need to add each Pipedrive user manually?
If a Pipedrive Global Admin integrates Pipedrive with TNZ, other users will automatically sync in.
Alternatively, setting up each Pipedrive user with a TNZ Dashboard login and getting each user to install Pipedrive is an effective option.
My Activities are duplicating and showing multiple times. Why?
If your messages are appearing multiple times as Activities, we may have multiple Global Admin users registered.
Contact TNZ and we'll adjust your account to prioritise one user as a Global Admin.
I'm seeing an 'Authorization Failed' Error. Why?
There are two leading causes for this error:
1. Your TNZ Dashboard login username is different to your Pipedrive login username. Add another TNZ User that matches your Pipedrive username, and switch to the new login and retry.
2. Your TNZ User's API Access has been corrupted. Get in touch with the TNZ Support Team and send them a screenshot of the error - they'll tackle this from the backend.