Create or Update User with Vero API on New Submission (Instant) from Jotform API

Pipedream makes it easy to connect APIs for Vero, Jotform and 2,400+ other apps remarkably fast.

Trigger workflow on

New Submission (Instant) from the Jotform API

Next, do this

Create or Update User with the Vero API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a Jotform trigger and Vero action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Submission (Instant) trigger
1. Connect your Jotform account
2. Optional- Select a Team
3. Select a Form
Configure the Create or Update User action
1. Connect your Vero account
2. Configure ID
3. Configure Email
4. Optional- Configure Channels
5. Optional- Configure Data
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Submission (Instant) on Jotform

Description:Emit new event when a form is submitted

Version:0.1.5

Key:jotform-new-submission

View on GitHub

Jotform Overview#

Jotform’s API is a powerhouse for automating form and survey data management. With Pipedream, harness this API to trigger workflows from new form submissions, manipulate and analyze your form data, and sync it across various platforms. Think streamlined data entry to CRMs, instant notifications for new leads or feedback, and timely data backups to cloud storage.

Trigger Code#

import jotform from "../../jotform.app.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  key: "jotform-new-submission",
  name: "New Submission (Instant)",
  description: "Emit new event when a form is submitted",
  version: "0.1.5",
  type: "source",
  dedupe: "unique",
  props: {
    jotform,
    http: "$.interface.http",
    teamId: {
      propDefinition: [
        jotform,
        "teamId",
      ],
    },
    formId: {
      propDefinition: [
        jotform,
        "formId",
        (c) => ({
          teamId: c.teamId,
          excludeDeleted: true,
        }),
      ],
    },
  },
  hooks: {
    async deploy() {
      const { content: form } = await this.jotform.getForm(this.formId, this.teamId);
      const { content: submissions } = await this.jotform.getFormSubmissions({
        formId: this.formId,
        teamId: this.teamId,
        params: {
          limit: 25,
          orderby: "created_at",
        },
      });
      for (let submission of submissions.reverse()) {
        const meta = {
          id: submission.id,
          summary: form.title,
          ts: Date.now(),
        };
        this.$emit(submission, meta);
      }
    },
    async activate() {
      return (await this.jotform.createHook({
        endpoint: this.http.endpoint,
        formId: this.formId,
        teamId: this.teamId,
      }));
    },
    async deactivate() {
      return (await this.jotform.deleteHook({
        endpoint: this.http.endpoint,
        formId: this.formId,
        teamId: this.teamId,
      }));
    },
  },
  async run(event) {
    const { body } = event;
    let { content: submission } = await this.jotform.getFormSubmission({
      submissionId: body.submissionID,
      teamId: this.teamId,
    });

    // insert answers from the webhook event
    const rawRequest = JSON.parse(body.rawRequest);
    for (const key of Object.keys(rawRequest)) {
      const regex = /^q(\d+)_/;
      const match = key.match(regex);
      if (match && match[1]) {
        submission.answers[match[1]].answer = rawRequest[key];
      }
    }

    this.$emit(submission, {
      summary: body.formTitle || JSON.stringify(body),
      id: body.submissionID,
      ts: Date.now(),
    });
  },
  sampleEmit,
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
Jotform	`jotform`	`app`	This component uses the Jotform app.
N/A	`http`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
Team	`teamId`	`string`	Select a value from the drop down menu.
Form	`formId`	`string`	Select a value from the drop down menu.

Trigger Authentication#

Jotform uses API keys for authentication. When you connect your Jotform account, Pipedream securely stores the keys so you can easily authenticate to Jotform APIs in both code and no-code steps.

About Jotform#

Jotform enables you to create online forms, collect responses directly in your email, and create fillable PDF forms.

Action#

Create or Update User on Vero

Description:This endpoint creates a new user profile if the user doesn't exist yet. Otherwise, the user profile is updated based on the properties provided. [See the documentation](https://developers.getvero.com/track-api-reference/#/operations/identify)

Version:0.0.2

Key:vero-create-or-update-user

View on GitHub

Vero Overview#

Vero's API allows you to automate email marketing tasks such as managing campaigns, users, and events. Integrating Vero with Pipedream enables you to create workflows that respond to various triggers, like webhooks or schedules, and carry out actions such as sending emails, segmenting users, or tracking events. This integration can be a powerful tool to personalize your marketing efforts and respond in real-time to your customers' interactions.

Action Code#

import { ConfigurationError } from "@pipedream/platform";
import app from "../../vero.app.mjs";

export default {
  type: "action",
  key: "vero-create-or-update-user",
  name: "Create or Update User",
  version: "0.0.2",
  description: "This endpoint creates a new user profile if the user doesn't exist yet. Otherwise, the user profile is updated based on the properties provided. [See the documentation](https://developers.getvero.com/track-api-reference/#/operations/identify)",
  props: {
    app,
    id: {
      propDefinition: [
        app,
        "id",
      ],
    },
    email: {
      propDefinition: [
        app,
        "email",
      ],
    },
    channels: {
      type: "string[]",
      label: "Channels",
      description: "A valid JSON array containing hashes of key/value pairs that represent the user's device token. Each hash should represent a single device token and include the fields type, address, and platform. Ex: `{\"type\":\"push\", \"address\":\"UNIQUE_DEVICE_TOKEN\", \"platform\":\"android\"}`",
      optional: true,
    },
    data: {
      type: "object",
      label: "Data",
      description: "A valid JSON hash containing key value pairs that represent the custom user properties you want to update. The locale, timezone and userAgent attributes are reserved properties that may be updated automatically by our SDKs. You can use these properties but bear in mind they may be overwritten if using our SDKs or integrations. All other keys are freeform and can be defined by you. Ex: `{\"first_name\":\"Damien\",\"last_name\":\"Brzoska\",\"timezone\":-10}`",
      optional: true,
    },
  },
  methods: {
    parseChannels(data) {
      if (!data) {
        return null;
      }
      const parsed = [];
      for (let i = 0; i < data.length; i++) {
        let item;
        try {
          item = JSON.parse(data[i]);
        } catch (err) {
          throw new ConfigurationError(`Invalid JSON in channels property at index ${i}: ${err.message}`);
        }

        if (Array.isArray(item)) {
          throw new ConfigurationError(`Invalid JSON in channels property at index ${i}: Expected an object, but received an array. If you want to send multiple items, please create a new child`);
        }

        parsed.push(item);
      }

      return parsed;
    },
  },
  async run({ $ }) {
    const {
      app,
      parseChannels,
      ...rest
    } = this;
    const res = await app.createOrUpdateUser({
      ...rest,
      channels: parseChannels(rest.channels),
    });
    $.export("summary", `User with id "${rest.id}" created or updated successfully`);
    return res;
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Vero	`app`	`app`	This component uses the Vero app.
ID	`id`	`string`	The unique identifier of the customer.
Email	`email`	`string`	The email address of the customer.
Channels	`channels`	`string[]`	A valid JSON array containing hashes of key/value pairs that represent the user's device token. Each hash should represent a single device token and include the fields type, address, and platform. Ex: `{"type":"push", "address":"UNIQUE_DEVICE_TOKEN", "platform":"android"}`
Data	`data`	`object`	A valid JSON hash containing key value pairs that represent the custom user properties you want to update. The locale, timezone and userAgent attributes are reserved properties that may be updated automatically by our SDKs. You can use these properties but bear in mind they may be overwritten if using our SDKs or integrations. All other keys are freeform and can be defined by you. Ex: `{"first_name":"Damien","last_name":"Brzoska","timezone":-10}`

Action Authentication#

Vero uses API keys for authentication. When you connect your Vero account, Pipedream securely stores the keys so you can easily authenticate to Vero APIs in both code and no-code steps.

To retrieve your Auth Token,

Navigate to your Vero account and sign in
Go to “Configuration” > “Settings” > “Project Details” > "API Credentials" > Auth Token

About Vero#

Game-changing multi-channel messaging tools for the next generation of marketers.

More Ways to Connect Vero + Jotform#

Other Popular Integrations#

Track Event for User with Vero API on New Submission (Instant) from Jotform API

Jotform + Vero

Try it

Popular Triggers#

New Submission (Instant) from the Jotform API

Emit new event when a form is submitted

Try it

Popular Actions#

Get Form Submissions with the Jotform API

Gets a list of form responses See the docs here

Try it

Get Monthly User Usage with the Jotform API

Gets number of form submissions received this month. Also, get number of SSL form submissions, payment form submissions and upload space used by user See the docs here

Try it

Get User Submissions with the Jotform API

Gets a list of all submissions for all forms on the account See the docs here

Try it

Create or Update User with the Vero API

This endpoint creates a new user profile if the user doesn't exist yet. Otherwise, the user profile is updated based on the properties provided. See the documentation

Try it

Track Event for User with the Vero API

This endpoint tracks an event for a specific user. If the user profile doesn't exist Vero will create it. See the documentation

Try it