To create an integration with Zapier there are two events to customize:
- Trigger: This watches for new or updated information. A trigger initiates an action in another application. In MC Professional, you can set up a trigger that initiates a Zap when you create, or cancel an event registration, and when a new member applies through a membership application form.
- Action: This pushes new or updated data into an application. You can push a new event registrant's data from MC professional into a spreadsheet or another application like GTR Events. You can also push data from a third party application to create new continuing education credits in your MC Professional database. Which action you can perform depends on the application.
Triggers available in MC Professional
In MC Professional the following triggers are available:
- Event Registrant Created
- Event Registrant Cancelled
- New member join from membership form
Event Registrant Created
When a member registers through the event section of a form, you can push the registrants submission data into a third party application. In Zapier, each Zap can only contain one event section. If you need to integrate event data for multiple events, you must create a new Zap for each event.
In Zapier, the events list displays the name of the event section, not the name of your form. If your form has more than one event section, it will display each section separately. You can search by Event Name or Event ID.
To find out the name of your event section in MC Professional, navigate to Forms > Form List > Edit the form > Click Properties in the event section, then view the Event Name field.
Archived and unpublished event forms still display in Zapier.
You can map all attributes and form fields included in your form (e.g. registrant name, selection sets, etc.).
In Zapier, these fields are labelled based on their Export Name.
The following form fields are available to map to a third party application:
- Date Registered: The date the form-taker registered for the event
- Submission ID: The ID tied to the form submission number
- Status: A member's status (e.g. active, lapsed, graced, etc.)
- Member Type: The registrant's member type in MC Professional
- Registered By: The form-taker that registered the profile for the event
- Discount Code: If included, the discount code the form-taker used
- User ID: A unique identifier assigned by the system for each member profile
- Amount Paid: The amount paid for the event
- Balance: The amount the form-taker still owes for the event
- id: The member's profile ID
- sectionId: The event id number, tied to the Event Section on the form
- formId: The form ID number (differs from the section ID)
Event Registrant Canceled
This trigger occurs when an admin cancels an event registration. You can push the following field data into a third party application:
- registrantId: A unique identifier tied to the registration number
- statusId: Displays 2, for canceled
- sectionId: The event ID tied to the Event Section on the form
New member join through membership form
Actions available in MC Professional
Actions will fail in MC Professional if you do not provide a unique identifier that maps to the correct member profile in your MC Professional database. You can use the attribute profile id, member number, or username as a unique identifier. The unique identifier provided must match an attribute of the same name in MC Professional.
In MC professional you can perform the following action:
Create Continuing Education Credit
You can map continuing education credits to a member's profile from a third party application. You must include the profile ID as a unique identifier. This must match the member's profile ID in your MC Professional database.
You can map the following fields from a third party application to a member profile in your MC Professional database:
If there's a trigger or action you would like included in MC Professional and Zapier, you can submit a feature request.