What is Zapier?

Being able to work independently is important, but everyone knows that for larger projects, you may need different people with different disciplines working together. The same is true for the apps that support your business. Unfortunately, different apps don’t always communicate as well as people do.

That’s where Zapier comes in. Zapier is a third-party service that connects your most important productivity tools, allowing you to create automatic workflows–or Zaps–between them.

Zapier integration means you’ll be able to connect Indy with other platforms and create Zaps based on triggers that happen within Indy.

Zapier integration is part of our Beta program and is available for Pro users. 
Features in Beta may behave in unexpected ways, and your feedback is always
appreciated. Once this feature leaves Beta, it will become a permanent part of
the Indy Pro suite.

For example, you can now automatically:

  • Send a Mailchimp campaign after receiving a new contact via forms

  • Receive SMS alerts when a contract is signed or a proposal is approved

  • Create a database in Notion to store your form responses

  • And much more

For the moment, this connectivity will be one-way. This means that events in Indy can only trigger actions in other apps and not the other way around–but keep an eye out for future updates.

Zapier Basics

Each Zap consists of a “trigger” and a resulting “action”. This means that when an event occurs in one application, that triggers an action in another.

Say you want to receive an SMS text message every time a contract gets signed in Indy. Your client signing the contract is the trigger, and the SMS text message you receive would be the resulting action.

Connecting Indy and Zapier

Before you do anything else, you need to make sure you have accounts on Indy, Zapier, and the app you want to connect with. The Zaps will not work otherwise.

  1. Log in to your Indy account and go to the Account Settings page.

  2. Once there, you’ll see an option called “Integrations” on your menu on the left of your screen. Everything related to Zapier integration will happen on this page.

  3. To start connecting the two, you’ll need to create an API key here on this page. Click on the “Generate API Key” button to get your key.

    Note: An API key is a series of letters and numbers used to authorize communication between apps. This is how Zapier will know it’s okay to connect with Indy.

  4. Click on the link to the invitation in step 1 of the “Next Step” banner. You should see this page inviting you to Indy’s public beta on Zapier. Accept the invite.

  5. Afterward, head on over to Zapier and log in there. Select “My Apps” from the menu on the left, then click on the “+ Add Connection” button. Search for Indy in the popup and select it from the dropdown. You should then be prompted to paste your API key. You’ll also have to write out Indy’s URL.

  6. Go back to the Zapier page in Indy and refresh it. If you see the words, “Zapier is connected!” directly above your API key, congratulations! You’ve successfully connected Indy and Zapier.

  7. Now that the two are connected, it’s time to start creating some Zaps!

Creating Zaps

Step 1: Set up a trigger in Indy

First things first, click “Create Zap”. Select Indy from the dropdown.

Afterward, choose an event from the list. This event will become the trigger for the Zap.

Once you’ve selected an event, you’ll be prompted to select an account, test your connection, and pick specific artifacts (forms, contracts, proposals, etc) that you want the Zap to apply to.

Step 2: Set up an action in another app

Time to finish creating the Zap. Select the app of your choice from the drop-down.

After you select the target app and the resulting action you want, Zapier will test the connection. Assuming there are no errors, you will have just created your first Zap!

If you don’t see an event trigger you want…

Please feel free to get in touch and let us know! Zapier integration will change with time, and we’re actively looking for areas where we can improve this experience.

Did this answer your question?