Skip to main content
Table of contents

How does it work?

Zapier can integrate many apps and systems with Plecto. Explore Zapier's integration catalog. To connect a system to Plecto with Zapier, you need to:

  1. Create a manual data source in Plecto.

  2. Configure a Zap in Zapier.

Read below for more detailed instructions on each of the steps.

Step 1: Create a manual data source in Plecto

First of all, you need a place where Zapier can send data from the integrated system. It means that you have to prepare a manual data source in Plecto. You will have to select this data source when setting up a Zap in Step 2.

  1. In Plecto, go to Data management > Data sources > + New data source > Custom input.

  2. Give the data source a title and click Save.

  3. (Optional) Add custom fields to your data source. In data source settings, click + Add field to create a new custom field. Fill in the details such as the field name and type. You can add as many fields as you need.

  4. Click Save in the bottom-right to finish.

Step 2: Configure Zap Trigger

  1. Open and click + Create Zap.

  2. Search for an app you want to pair with Plecto.

  3. Choose an event such as new email, new sign-up, or other events available in your selection. This event will prompt Zapier to send information to Plecto.

  4. Click Continue.

  5. Sign in to your account if necessary. Click Continue.

  6. The trigger setup might differ depending on what app you're connecting. Fill in any required fields and click Continue.

  7. Click Test trigger. If all the provided details are correct, Zapier should be able to find the event. Click Continue to move on to configuring the Action.

Step 3: Configure Zap Action

  1. Search for Plecto.

  2. Under Event, choose Create New Registration.

  3. Click Continue.

  4. Choose your Plecto account or connect a new one. Click Continue.

  5. Now for the fun part – Zapier needs to know how to put the data in your Plecto data source, so you need to tell it exactly where you want it.

    1. Integration Name – Freely choose an integration name. Plecto thinks of Zapier as integration, and the name you add here will appear in our system. If you plan to create multiple Zaps in the future, use the same integration name (case sensitive) to avoid generating duplicate employee profiles in Plecto.

    2. User ID – This field represents the user ID from the external system. Here you can either select a dynamic value from the list or type in a static value.

    3. User Name – This name will show in the Employee field in your Plecto data source.

    4. Data Source – Select the manual data source you created in step 1.

    5. Date (optional) – If the integration allows you to add a date, this information will show in the Created date field in your data source.

    6. External ID – This will be a unique ID of each registration that gets created in Plecto. You can select a dynamic value from the dropdown list (something that looks similar to an ID). Your first registration will have this ID, and all new registrations will generate unique IDs. If you type in any values manually, Zapier will only create one registration in the data source and overwrite it every time it sends new data (you will only have one registration).

    7. If your data source contains more fields, let Zapier know what you want to see in them.

  6. Once you're ready, click Continue.

  7. Click Test & continue.

  8. If everything works, click Publish Zap.

Static and dynamic values

  • Static values are fixed, the same for each registration. If your external system is the only "user" creating registrations in your Plecto data source, we recommend adding static values to the User ID and User Name fields, for example, Calendly and 1. This will import only one employee into Plecto (create one employee profile), and all registrations will be made on behalf of this employee.

  • Dynamic values (selected from the dropdown list in Zapier) are changing values. If you add a dynamic user ID, Plecto will create new employee profiles for each new user that gets imported.

We recommend selecting a dynamic value in the External ID field, for example, ID: 12345. This will make sure to generate unique IDs for each new registration upon their creation. If you don't select a dynamic value here, Zapier will overwrite the same registration.