Aloware and Zapier: Trigger and Action Integration

Aloware's Zapier Integration automates contact management with triggers for updates and supported fields.

Laarni D avatar
Written by Laarni D
Updated over a week ago

Why Integrate Aloware with Zapier?

Integrating Aloware with Zapier is crucial for users looking to automate and streamline their contact management processes across various applications. Zapier serves as a bridge, enabling Aloware to connect with over 3,000 web apps, even if they don't have direct integrations with Aloware.

This integration eliminates manual data entry, reduces human error, and ensures contact information remains consistent across platforms.

It is particularly valuable for sales teams, marketers, and customer support representatives who rely on efficient contact management and communication.


Key Benefits of Aloware-Zapier Integration

  1. Automate Action Inside Aloware

    Events that occur outside of Aloware can automatically trigger actions within Aloware. For example:

    1. Create or Update Contacts: When a contact submits their information through a web form, Zapier can automatically create a contact in Aloware.

    2. Send SMS Messages: Automatically send SMS messages to Aloware contacts based on external events.


      Example: A contact visits your site, becomes interested in your service, and submits their info on your web form. Use Aloware's Zapier integration to automatically create a contact in Aloware from the webform submission.

  2. Automate Action Outside Aloware

    Events within Aloware can trigger actions in other apps connected through Zapier. For example:

    1. Enroll Contacts in Marketing Campaigns: Automatically enroll new contacts created in Aloware into MailChimp marketing campaigns.

    2. Update CRM Systems: Sync contact updates in Aloware with CRM systems like Salesforce.

      Example: An agent creates a new contact in Aloware. Automatically enroll this contact into a MailChimp Marketing campaign.


How it Works

Zap automates tasks between Aloware and your chosen business app.

  1. Triggers initiate workflows (Zaps) when specific events occur in Aloware, such as:

    1. Call Disposed - Triggers when a call is marked as completed in Aloware. This can initiate follow-up actions, such as sending a summary email or updating a CRM system.

    2. Communication Disposed - Triggers when any type of communication (e.g., call, SMS) is completed in Aloware. This can be used to log the communication details in external apps or trigger other follow-up actions.

    3. Communication Initiated - Triggers when a new communication is started in Aloware. This can help log communication start times or notify team members of new activities.

    4. Contact Created - Triggers when a new contact is added to Aloware. This can automatically add the contact to marketing campaigns or CRM systems, ensuring no new lead is missed.

    5. Contact Disposed - Triggers when a contact's status is changed or when they are removed from a list. This can help maintain up-to-date records in external systems by reflecting these changes.

    6. Contact Updated - Triggers when an existing contact’s information is updated in Aloware. This ensures all platforms have the latest contact details, enhancing data consistency across tools.

    7. Recording Saved - Triggers when a call recording is saved in Aloware. This can be used to store recordings in cloud storage or link them to customer profiles in a CRM.

    8. Voicemail Saved - Triggers when a voicemail is saved in Aloware. This can notify team members of new voicemails or store them for future reference.

  2. Action are the steps performed by the Zaps, such as:

    • Create/Update Contact - Adds a new contact or updates an existing contact's information in Aloware. This ensures your contact list is always current and accurate across all integrated platforms.

    • Enroll Contact to Sequence - Automatically enroll a contact into a predefined sequence in Aloware, such as a marketing drip campaign. This helps in nurturing leads and keeping them engaged without manual intervention.

    • Establish Two-Legged Call - Set up a two-way call between an agent and a contact through Aloware. This can be used for quick follow-ups or scheduled calls, enhancing communication efficiency.

    • Number Lookup - Searches for information about a phone number, such as its carrier or location, using Aloware. This helps in verifying contact information and targeting communications more effectively.

    • Send RVM (Ringless Voicemail) - Sends a ringless voicemail to a contact's phone number through Aloware. This is useful for delivering messages directly to voicemail without disturbing the contact.

    • Send SMS - Sends an SMS message to a contact through Aloware. This can be used for appointment reminders, follow-ups, or promotional messages, ensuring timely communication.


Supported Fields for Integration

  1. [campaign_id] - [required] Aloware campaign ID (from the campaign’s page) that this lead needs to be attached to.

  2. [phone_number] - [required] The lead’s phone number, in any format +1 818-740-5020, +1 818-740-5020, +1 818-740-5020, etc.).

  3. [company name] - [optional] Contact's company affiliated to.

  4. [name] [first_name] [last_name] - [optional] Contact identifiers.

  5. [lead source] - [optional] A custom source field to segment the contacts later.

  6. [source] - [optional] A custom source field to segment the contacts later.

  7. [email] - [optional] Contact identifier for CRM integrations.

  8. [date_of_birth] - [optional] Contact’s birthday, in US format (12/05/1975 or 12-05-1975) for birthday campaigns.

  9. [timezone] - [optional] Contact’s timezone for scheduling purposes.

  10. [city], [state], [zip code], [country] - Contact’s geographical location for segmentation, optional. If blank, these values will be determined from the phone number.

  11. [address] - [optional] Contact's location.

  12. [website] - [optional] A custom field for the contact's business website.

  13. [notes] - Customer details on the Notes section of Aloware contacts. Use this field to capture your contact’s consent to electronic communications.

  14. [lead_source] - Exemple: Google Ads

  15. [csf1][csf2] - Custom data

  16. [user-id][user_email] - Aloware user identifiers that can be used as contact owner.

  17. [ring_group_id] - If yes, we will randomly assign it to an agent/user within a ring group and override the selected user.

  18. [ring_group_id] - Select one of your Aloware ring groups (We will check this field if the distribute to ring group option is selected.)

  19. [check_available_users] - if the value is Yes and no active user found, contact will not be distributed within a ring group (We will check this field if the distribute to ring group option is selected.)

  20. [add_to_powerdialer] - Should we add the contact to the PowerDialer of agent/user where it is distributed? If the lead is already in someone’s PowerDialer, it will be skipped.

  21. [powerdialer_position] - Combined with the option above, should this lead go to the top of the PowerDialer or bottom?

  22. [sequence_id] - Select one of your Aloware sequences to enroll the lead to it.

  23. [force_update_sequence] - Should we disenroll this lead from other automation sequences and push them to a new one? (We will check this field if a sequence is selected).

  24. [force_update] - Should we override existing data and update the contact information?

  25. [line_id] - Select one of your Aloware lines as the initial contact line or to send from (in Establish Two-Legged Cal, in Send RVM and in Send SMS).

  26. [tag_id] - Tag your lead with an Aloware tag.

  27. [disposition_status_id] - Add a disposition status to the lead.

  28. [other_phone_numbers] - Example: Mobile, Whatsapp.

  29. [audio_url] - The download URL of the audio file to be sent.

  30. [message] - The message that you want to send to the contact.

  31. [image_url] - Optional media file to be sent alongside the message.

Integrating Aloware with Zapier is essential for businesses seeking to optimize their workflows, improve efficiency, and maintain seamless communication across various platforms. This integration allows users to focus on strategic tasks while automated processes handle routine actions, driving better business outcomes.

Did this answer your question?