​What is Zapier?

Zapier is a web-based tool that allows users to build automation workflows between thousands of supported web applications and platforms. It provides a simple user interface to design and build cross-platform workflows to synchronise data for things like lead and financial events. To learn more about Zapier, visit: http://zapier.com.

Key Zapier terms

• Zap. An automated workflow.

• Trigger. Event that begins the sequence.

• Action. Event that occurs as a result of a trigger.

• Tasks. A single event within an activated Zap, such as a filter check (ie. automation rule

• Webhook URL. URL generated by Zapier, added in Edvisor for trigger Zaps.

Connection setup

Three main steps:

1. Allow Zapier to access Edvisor via Zapier invite link (Edvisor isn't on the public directory).

2. Connect the Edvisor account using an Edvisor-provided API key.

3. Send Edvisor team the Zapier-generated webhook URL via the Webhooks Request Form (for trigger Zaps).

Webhook Request Form

Zapier invite link

In order to connect Edvisor and Zapier, it is required that you have independent, non-outstanding, accounts with both services.

Edvisor is not listed on Zapier’s public directory; but can be added by using our Zapier invite link here:

https://zapier.com/developer/invite/74188/3ddb3b8d50982cb067c35a26d55114c3/

1. Open a new browser or tab and log in to your pre-existing Zapier account

2. Click or copy the link above to open the page

3. Accept the invite

4. Begin your new, first ‘Zap’ using Edvisor as the trigger event (optional)

Also, have your Edvisor (private) API key ready. this can be requested from your Account Manager or our Support Team and will look something like this:

private_yp3779t2wnklwj1zfluq535hj0xzjqujj44m

If you are new to Zapier and want to learn more, check out their content on YouTube.

What Zapier can do with Edvisor

Limited to student profile events:

• Create or update student profiles.

• Pipeline step/stage movement.

• Default and custom student fields.

Zapier cannot access: quotes, invoices, agreements, or other non-student data.

Pro Tip - Before creating or testing Zaps:

1. Log into Edvisor.

2. Create or update a student record (this real event is used to test the trigger).

3. Verify field mapping in Zapier.

Useful IDs

• UserID of agents — ask Account Manager or Support.

• Pipeline ID and stage IDs — visible in Settings > Company > Pipelines (number beside each pipeline stage).

It is highly recommended that before you begin creating or testing your Zaps, to log into Edvisor and create or update a student record respectively. This record (event) is then used throughout the Zap creation process to test triggers as well as verify your desired field mapping.

Edvisor as a Trigger Event

There are two trigger event types possible from Edvisor.

• Student Created

• Student Updated

Below is an example of creating a new Zap using Edvisor as a trigger event, where the type is ‘Student Created’, but can be changed to ‘Student Updated’:

To begin setting up your trigger, you will need to provide the Edvisor team your Zapier Webhook URL for our team to assign to your Edvisor account. Generated by Zapier for each 'zap', this URL needs to be added by our team.

We recommend preparing several Edvisor trigger Zaps in advance, as multiple webhooks can be added for you as a batch.

To request webhooks to be added, please use our form below and be sure to indicate the event type that corresponds to the webhook URL.

Webhooks Request Form

Once the webhook is connected, you will be able to proceed with the Zap creation - adding your action event (app), and your additional steps. It will be important to know the fields and value formats that is accepted by your action app (destination).

Edvisor as an Action Event

When using Edvisor as the action app, you will need to consider the accepted formatting of the fields when mapping your Zaps.

For any incompatible formats, it is important use the formatting step. Or, you can also use the javascript code step to provide the data to map. Some common fields to consider, below.

Birthdate: YYYY-MM-DD

The only accepted format for dates in Edvisor.

Nationality: Numerical Code

Edvisor uses the standard, ISO 3166 country codes, due to the need for precise and consistent nationality data. However, the field is modified in Zapier by using a numerical ID number from our databases and this ID must be used in Zapier order to reflect the proper mapping to ‘Nationality’. Refer to this list of Edvisor Country Codes and IDs

For more info, refer to this public article about ISO 3166 country codes.

Common examples:

Brazil = 29

Mexico = 148

Colombia = 46

Spain = 64

France = 70

Turkey = 212

Italy = 102

Germany = 54

China = 45

Japan = 106

S. Korea = 114

Locations: GoogleplaceID (alphanumeric)

To update or create city and country (location) information to Edvisor accurately, the location data must be converted into a GooglePlaceID format. Edvisor uses this for accuracy, and allows for the dropdown logic of this field.

In order to apply this to Zapier, you must add a javascript code step between your trigger and (Edvisor) action event. This is slightly more advanced technically, and to find out specifics about how to implement Javascript code steps into your Zaps, go here.

When you have added the step, paste this code to be able to map the output value to the location fields of your action event (Edvisor):

currentLocation: '',
destinationLocation: ''
};
if (inputData.currentLocation && inputData.currentLocation.trim()) {
   output.currentLocation = inputData.currentLocation;
}
if (inputData.destinationLocation && inputData.destinationLocation.trim()) {
   output.destinationLocation = inputData.destinationLocation;
}

For a more complete list of Edvisor’s accepted formatting, refer to:

Importing Students - Customer Guide

Troubleshooting

If you are having some trouble verifying your Zap steps, here are some helpful tips to to consider:

1. Create a new student or make a new Edit to a student profile in Edvisor. This will help to provide the latest data for you to test and verify your field mapping. Once you do this, make sure to refresh your fields in Step #1 of your Zaps.

2. Reduce the amount of field mapping to Edvisor (as the action event) to pinpoint an error value. It is possible the formats are still providing an error, and it may not be easy to tell which one. If this is the case, reduce or remove the number of fields you are mapping, and re-map each field, testing the step after each addition.

3. Zapier themselves provide some great troubleshooting tips that are universal. Try look for an answer here: Troubleshoot errors in Zapier

Finally, if you are still having issues, setup a chat with our Support Team to coordinate a call to walk through your Edvisor Zap - support@edvsior.io