Track Event for User with Vero API on New event when the content of the URL changes. from HTTP / Webhook API

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

Trigger workflow on

New event when the content of the URL changes. from the HTTP / Webhook API

Next, do this

Track Event for 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 HTTP / Webhook 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 event when the content of the URL changes. trigger
1. Connect your HTTP / Webhook account
2. Configure Watching timer
3. Configure HTTP Request Configuration
4. Configure Emit body only
5. Configure Emit as array
Configure the Track Event for User action
1. Connect your Vero account
2. Optional- Configure ID
3. Optional- Configure Email
4. Configure Event Name
5. Optional- Configure Data
6. Optional- Configure Extras
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 event when the content of the URL changes. on HTTP / Webhook

Description:Emit new event when the content of the URL changes.

Version:0.0.2

Key:http-watch-url

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

import http from "../../http.app.mjs";
import hash from "object-hash";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";

export default {
  key: "http-watch-url",
  name: "New event when the content of the URL changes.",
  description: "Emit new event when the content of the URL changes.",
  version: "0.0.2",
  type: "source",
  dedupe: "unique",
  props: {
    http,
    timer: {
      type: "$.interface.timer",
      label: "Watching timer",
      description: "How often to watch the URL.",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },
    },
    httpRequest: {
      type: "http_request",
      label: "HTTP Request Configuration",
      description: "HTTP Request Configuration",
      default: {
        method: "GET",
      },
    },
    emitBodyOnly: {
      label: "Emit body only",
      description: "If set as true the emitted item will contain only the response body, otherwise, it will include the request status code.",
      type: "boolean",
      default: true,
    },
    emitAsArray: {
      label: "Emit as array",
      description: "If the request responds with an array, this source will emit changes individually for each item of the array.",
      type: "boolean",
      default: false,
    },
  },
  methods: {
    getMeta(data, status) {
      if (this.emitBodyOnly) {
        return data;
      }
      return {
        data,
        status,
      };
    },
    emitArray(event, response) {
      if (!Array.isArray(response.data)) {
        return this.emitAny(event, response);
      }
      for (const item of response.data) {
        const meta = this.getMeta(item, response.status);
        this.emit(event, meta);
      }
    },
    emitAny(event, response) {
      const meta = this.getMeta(response.data, response.status);
      this.emit(event, meta);
    },
    emit(event, meta) {
      const ts = event.timestamp || Math.round(Date.now() / 1000);
      this.$emit(meta, {
        id: hash(meta),
        summary: `Requested at ${ts}`,
        ts,
      });
    },
  },
  async run(event) {
    const response = await this.httpRequest.execute();
    if (this.emitAsArray) {
      this.emitArray(event, response);
    } else {
      this.emitAny(event, response);
    }
  },
};

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
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.
Watching timer	`timer`	`$.interface.timer`	How often to watch the URL.
HTTP Request Configuration	`httpRequest`	`http_request`	HTTP Request Configuration
Emit body only	`emitBodyOnly`	`boolean`	If set as true the emitted item will contain only the response body, otherwise, it will include the request status code.
Emit as array	`emitAsArray`	`boolean`	If the request responds with an array, this source will emit changes individually for each item of the array.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

Track Event for User on Vero

Description:This endpoint tracks an event for a specific user. If the user profile doesn't exist Vero will create it. [See the documentation](https://developers.getvero.com/track-api-reference/#/operations/track)

Version:0.0.1

Key:vero-track-event-for-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-track-event-for-user",
  name: "Track Event for User",
  version: "0.0.1",
  description: "This endpoint tracks an event for a specific user. If the user profile doesn't exist Vero will create it. [See the documentation](https://developers.getvero.com/track-api-reference/#/operations/track)",
  props: {
    app,
    id: {
      propDefinition: [
        app,
        "id",
      ],
      description: "The unique identifier of the customer. You must provider either `id` or `email`.",
      optional: true,
    },
    email: {
      propDefinition: [
        app,
        "email",
      ],
      description: "The email address of the customer. You must provider either `id` or `email`.",
      optional: true,
    },
    eventName: {
      type: "string",
      label: "Event Name",
      description: "The name of the event tracked.",
    },
    data: {
      type: "object",
      label: "Data",
      description: "A valid JSON hash containing key value pairs that represent the custom user properties you want to track with the event. All keys are freeform and can be defined by you.",
      optional: true,
    },
    extras: {
      type: "object",
      label: "Extras",
      description: "A valid JSON hash containing key/value pairs that represent the reserved, Vero-specific `created_at` and `source` properties.",
      optional: true,
    },
  },
  async run({ $ }) {
    if (!this.id && !this.email) {
      throw new ConfigurationError("You must provide either an `id` or an `email` to create or update a user");
    }

    const res = await this.app.trackEventForUser({
      identity: {
        id: this.id,
        email: this.email,
      },
      event_name: this.eventName,
      data: this.data,
      extras: this.extras,
    });
    $.export("summary", `Track successfully create for user ${this.id || this.email}`);
    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. You must provider either `id` or `email`.
Email	`email`	`string`	The email address of the customer. You must provider either `id` or `email`.
Event Name	`eventName`	`string`	The name of the event tracked.
Data	`data`	`object`	A valid JSON hash containing key value pairs that represent the custom user properties you want to track with the event. All keys are freeform and can be defined by you.
Extras	`extras`	`object`	A valid JSON hash containing key/value pairs that represent the reserved, Vero-specific `created_at` and `source` properties.

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 + HTTP / Webhook#

Other Popular Integrations#

Create or Update User with Vero API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Vero

Try it

Create or Update User with Vero API on New Requests from HTTP / Webhook API

HTTP / Webhook + Vero

Try it

Track Event for User with Vero API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Vero

Try it

Track Event for User with Vero API on New Requests from HTTP / Webhook API

HTTP / Webhook + Vero

Try it

Create or Update User with Vero API on New event when the content of the URL changes. from HTTP / Webhook API

HTTP / Webhook + Vero

Try it

Popular Triggers#

New Requests from the HTTP / Webhook API

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Try it

New Requests (Payload Only) from the HTTP / Webhook API

Get a URL and emit the HTTP body as an event on every request

Try it

New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

Try it