Execute SQL Query with PostgreSQL API on Contact Deactivated from Vision6 API

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

Trigger workflow on

Contact Deactivated from the Vision6 API

Next, do this

Execute SQL Query with the PostgreSQL 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 Vision6 trigger and PostgreSQL action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the Contact Deactivated trigger
1. Connect your Vision6 account
2. Configure timer
3. Select a List
Configure the Execute SQL Query action
1. Connect your PostgreSQL account
2. Configure PostreSQL Query
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#

Contact Deactivated on Vision6

Description:Emit new event when a contact is deactivated

Version:0.0.2

Key:vision6-contact-deactivated

View on GitHub

Vision6 Overview#

The Vision6 API offers a powerful way to automate email marketing and audience engagement directly through Pipedream. With it, you can programmatically manage lists, contacts, and messages, and also track campaign performance. This API provides granular control over email workflows, enabling custom triggers, targeted actions, and detailed analytics retrieval. The combination of Vision6 with Pipedream's serverless platform unlocks endless possibilities for syncing data, personalizing communication, and optimizing marketing strategies without manual intervention.

Trigger Code#

import common from "../common/base.mjs";

export default {
  ...common,
  key: "vision6-contact-deactivated",
  name: "Contact Deactivated",
  description: "Emit new event when a contact is deactivated",
  version: "0.0.2",
  type: "source",
  dedupe: "unique",
  methods: {
    ...common.methods,
    async getHistoricalEvents(limit) {
      const contacts = await this.getPaginatedContacts(this.list, {
        is_active: false,
      });
      // create log of inactiveIds
      const inactiveIds = contacts.map((contact) => contact.id);
      this._setIds(inactiveIds);

      return contacts.slice(0, limit);
    },
    isNewlyDeactivated(contact, inactiveIds) {
      return !contact.is_active && !inactiveIds.includes(contact.id);
    },
    isNewlyActivated(contact, inactiveIds) {
      return !contact.is_active && inactiveIds.includes(contact.id);
    },
    async getContacts(since) {
      const deactivatedContacts = [];
      let inactiveIds = this._getIds();
      const contacts = await this.getPaginatedContacts(this.list, {
        ["last_modified_time:in"]: this.formatSinceDate(since),
      });
      for (const contact of contacts) {
        if (this.isNewlyDeactivated(contact, inactiveIds)) {
          inactiveIds.push(contact.id);
          deactivatedContacts.push(contact);
        } else if (this.isNewlyActivated(contact, inactiveIds)) {
          inactiveIds = inactiveIds.filter((id) => id !== contact.id);
        }
      }
      this._setIds(inactiveIds);
      return deactivatedContacts;
    },
    generateMeta(contact) {
      const ts = Date.parse(contact.last_modified_time);
      return {
        id: `${contact.id}${ts}`,
        summary: `Deactivated Contact ID: ${contact.id}`,
        ts,
      };
    },
  },
};

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
Vision6	`vision6`	`app`	This component uses the Vision6 app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
	`timer`	`$.interface.timer`
List	`list`	`integer`	Select a value from the drop down menu.

Trigger Authentication#

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

You can get your API Key and Region from the Integrations page in your Vision6 account, on the API Keys tab.
Your region is us1 if your Vision6 REST API Endpoint is https://us1.api.vision6.com/

About Vision6#

Australia's Most Reliable Email & SMS Marketing Software. Sign Up for a Free Trial Today!

Action#

Execute SQL Query on PostgreSQL

Description:Execute a custom PostgreSQL query. See [our docs](https://pipedream.com/docs/databases/working-with-sql) to learn more about working with SQL in Pipedream.

Version:3.0.1

Key:postgresql-execute-custom-query

View on GitHub

PostgreSQL Overview#

On Pipedream, you can leverage the PostgreSQL app to create workflows that automate database operations, synchronize data across platforms, and react to database events in real-time. Think handling new row entries, updating records from webhooks, or even compiling reports on a set schedule. Pipedream's serverless platform provides a powerful way to connect PostgreSQL with a variety of apps, enabling you to create tailored automation that fits your specific needs.

Action Code#

import postgresql from "../../postgresql.app.mjs";

export default {
  name: "Execute SQL Query",
  key: "postgresql-execute-custom-query",
  description: "Execute a custom PostgreSQL query. See [our docs](https://pipedream.com/docs/databases/working-with-sql) to learn more about working with SQL in Pipedream.",
  version: "3.0.1",
  type: "action",
  props: {
    postgresql,
    // eslint-disable-next-line pipedream/props-description
    sql: {
      type: "sql",
      auth: {
        app: "postgresql",
      },
      label: "PostreSQL Query",
    },
  },
  async run({ $ }) {
    const args = this.postgresql.executeQueryAdapter(this.sql);
    const data = await this.postgresql.executeQuery(args);
    $.export("$summary", `Returned ${data.length} ${data.length === 1
      ? "row"
      : "rows"}`);
    return data;
  },
};

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
PostgreSQL	`postgresql`	`app`	This component uses the PostgreSQL app.
PostreSQL Query	`sql`	`sql`

Action Authentication#

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

Connecting to Restricted Databases

Either enable the shared static IP for this account below, or configure a VPC to deploy any workflow in your workspace to a private network with a dedicated static IP. Learn more in our docs.

SSL Setup

Configure SSL on your PostgreSQL database by providing the CA (Certificate Authority), and choosing between Full Verification, Verify Certificate Authority (CA), or Skip Verification. Skipping verification is not recommended as this has serious security implications.