You can use Zapier to integrate Norby with the rest of your stack and create custom workflows with other tools.
How does this work?
Zapier is a tool for creating custom workflows by linking together triggers from one application and actions in another. A trigger can contain a payload with metadata which can be read by the receiving application to perform some action.
For instance, a Norby trigger might be when someone registers for your event; the payload on the trigger would include the person's email address and any other information you chose to collect. You can use Zapier to map this trigger to a receiving action in another application like Mailchimp to automatically import event registrations to a mailing list.
That's just the beginning, though – there's tons you can do with Norby and Zapier! Read on to learn how.
Adding Norby to Zapier
Before you can use Norby triggers in your zaps, you first need to connect Norby to your Zapier account. Head over to your Norby dashboard and click Connect Accounts or open the organization menu in the bottom left corner and click Integrations.
From there, scroll down to the Zapier section and click the Connect button.
Follow the prompts to create a Zapier account or log into your existing account. After creating an account or logging in, you'll be presented with an invite to join the Norby Beta on Zapier. Click Accept Invite & Build a Zap to finish adding Norby to your Zapier account.
Creating a Zap
Now that you've installed Norby in your Zapier account, you can create new zaps using Norby triggers.
Create a new zap and search for Norby to set up your first trigger.
Zapier will then ask you what Norby event you'd like to use to trigger your workflow. Norby currently supports two flexible triggers.
This trigger is fired whenever a user registers for an event, purchases a ticket, or signs up for a Drop. The payload will include details about their registration, identifying information you've chosen to collect like their email or name, and responses to any custom form fields or survey questions you've added.
The New RSVP trigger is useful for connecting Norby to external CRMs and marketing providers like Mailchimp, Klaviyo, Flodesk, or ActiveCampaign. For instance, if you're collecting emails for an event you can send each registration to a particular list or segment in Mailchimp and use that for your email marketing.
This trigger is fired whenever events or Drops are created, updated, or deleted. The payload will include details about the type of action that was performed as well as metadata for the given event or Drop.
The Content trigger is useful for connecting Norby to external content management systems like Wordpress. For instance, you can create a new signup page in Wordpress whenever a Drop is published and automatically embed the Drop signup button in the body of the page.
After choosing the trigger you'd like to use, Zapier will ask you to authenticate the connection to your Norby account. Click Sign in to Norby to proceed.
Zapier will then ask for your Norby API key, which will be used to authenticate your zaps. You can find this key back in the Integrations section of your Norby dashboard where you first hit the Connect button to begin linking Zapier to your account.
Copy your Norby API key and paste it into the Zapier pop up window. After successfully verifying your connection, you'll be able to return to the Zapier workflow editor and click Continue.
In this example, we're using the New RSVP trigger to send email registrations to ActiveCampaign. Zapier will show you an example of what a New RSVP payload might look like with fake data in it; you can ignore this and click Continue.
Finally, choose the app you want to connect on the receiving end of the Zap. In this example, we're connecting Norby to ActiveCampaign and forwarding email registrations. All we have to do is map the email found in the New RSVP payload to the appropriate field in ActiveCampaign.
And that's it, you're done!
After setting up your workflow, Zapier will offer you the opportunity to test your workflow with an example payload. The example payload includes fake data – for instance, the email specified is "email@example.com" – and some receiving apps may reject that fake data. For instance, Mailchimp has been known to reject "firstname.lastname@example.org" as a fake email address.
For this reason, testing your Zapier workflow with the fake data may fail depending on what app you choose to connect on the receiving end. If this happens, that does not mean the workflow isn't set up correctly or won't work, it just means the example payload is being rejected.
You can simply skip the testing step and go straight to enabling your workflow and try testing it yourself by registering for something or updating content on your Norby and triggering the workflow.
*Last updated 3/31/2021*