Last Updated: 2021-01-05

Grouparoo imports data into customer profiles using sources. This type of plugin defines an App and one more Connections with the import direction. The same plugin can also make destinations, but this document focuses on how to make a source.

A source will define how Grouparoo should import properties into profiles. An example property might be firstName and the postgres plugin knows how to fill that out for a user by querying the database.

Sources also can define schedules. These know how to connect with the data to know what has changed. A change will trigger profiles and their properties being updated. Schedules are often recurring.


An App represents the ability to communicate with a source. For example, this could mean server address and credentials for a data warehouse.

The properties (PluginApp) of an App are:

  • name: The user-facing name of the app. For example, snowflake or postgres.

  • options: Options needed to configure and connect to your app. This might commonly be an apiKey or username and password. Options have key (string), displayName (string), description (string), placeholder (string), and required (boolean) attributes.

  • icon: The path to the app's icon file (SVG or PNG). Icons should be stored in the /public directory of your plugin.

  • App Methods

    These methods are used to configure and interact with the app.

    • test TestPluginMethod This method will be called when an app is created to ensure that the app can be reached. The appOptions and other data will be passed to it. The test method should whether it can connect with those options or not, along with a message. This will often use the connect result to verify success.
    • connect ConnectPluginAppMethod If defined, this method is called to get an instance of a client to the source. It uses the appOptions passed to it to return an object that knows how to make queries. It will cache the client and give it to Connection methods. If it is not defined, the Connection (import) methods will be expected to connect each time. Using connect results in higher efficiency sources. For example, the postgres plugin uses this to keep a socket open with the database server.
    • disconnect DisconnectPluginAppMethod When defining connect, this method is used to disconnect the client. For example, to close the Postgres socket when the server is shutting down.


Your plugin can provide multiple types of Connections for use within Grouparoo. Connections use Apps to import or export data. In the source case, this is about the import direction.

The properties (PluginConnection) of a source Connection are:

  • name: The user-facing name of the connection, like snowflake-query-import or postgres-table-import.

  • direction: Use import for sources.

  • description: The user-facing description of the connection.

  • app: The name of the app created before. For example, your snowflake-query-import connection might require the snowflake app, also defined by your plugin.

  • options: Options needed to configure this connection. This differs from the options of an app, and is likely dependent on the app options. For example, an postgres-table-import connection requires a table option to be set by the Grouparoo user, and will use the name, host, password and database options from the postgres app that it is used to get the list of table names.

  • propertyOptions: Options needed to configure each property. Each has a these fields: key, displayName, required, description, type. You can also define an options method to define the option dynamically. For example, the postgres-table-import connection needs a column name to import the data for the property.

  • scheduleOptions: Options needed to configure a schedule. Each has a these fields: key, required, description, type. You can also define an options method to define the option dynamically. For example, the postgres-table-import connection needs a column name to known which column is the "updated_at" timestamp.

  • Source Methods

    These methods are used in the creation of a source with properties.

    • sourceOptions SourceOptionsMethod This allows more dynamic options to be specified. For example, it could also use code to provide a set of choices for a list selection. For example, the postgres-table-import connection lists out table names.
    • sourcePreview SourcePreviewMethod Show the user a preview of the data. Given the current options, if possible return a preview. For example, the postgres-table-import returns 10 rows from the selected table.
    • sourceFilters SourceFilterMethod During property creation, this allows the plugin to determine what filters are available. For example, the postgres-table-import notes that integers columns have actions such as greater than and string columns have different filters such as like.
    • uniquePropertyBootstrapOptions UniquePropertyBootstrapOptions: There is an interesting case during creation of the first source. It's possible that the first source (Postgres User Table) might need one of it's own properties (user_id) to bootstrap the rest. This allows a source to define the options that such a property would use.
  • Property Methods

    One of these should be defined. The choice is whether or not the plugin can import many users at once for a property or it is done one at a time.

    • profileProperty ProfilePropertyPluginMethod Given a profile and the property definition, get the value of the property for that profile.
    • profileProperties ProfilePropertiesPluginMethod Given an array of profiles and the property definition, get the value of the property for each profile.
  • Schedule Methods

    These methods are used when the source can have a schedule.

    • profiles ProfilesPluginMethod This method is the core method to implement a schedule. It uses a high-water mark and given options to return a collection of profiles to import. This options might also return properties to set on the profiles The main goal of this method is to call await plugin.createImport(schedule, run, row) for each row of data, where row is an object like {user_id: 9, email: "", first_name: "person"}
    • sourceRunPercentComplete SourceRunPercentCompleteMethod If implemented, this method can help the user by getting a percentage that an import session is complete. SQL sources tend divide how many imports have been done by the number of total records since the last change.

When defining methods, link to the method directly, do not use a string name.

SQL Sources

Most SQL-based sources implement two connections: table and query.

The table source is optimized for the common case where the data to import is a table with a foreign key to a unique property. An example might be a "purchases" table with a "user_id" column. A simple "users" table with an "id" column also works. In these cases, this source allows the user to sum, count, and perform other operations without writing any SQL. This also makes it each to make schedules and optimize the import speed.

The query source allows someone to write any SQL. It uses a mustache templating system to be able to use another other property. For example: SELECT SUM(price) FROM purchases INNER JOIN users ON ... WHERE = {userId}. This flexibility makes it less performant on large datasets because it fetches property values one profile at a time.

Both of these SQL sources tend to recalculate their properties each time a profile change is detected and the profile is being recalculated. This keeps things nice and update-to-date.

Schedule Sources

Another class of source runs more off data pulled during the schedule phase than fetching properties. For example, the Google Sheets source will connect to a spreadsheet and note the cell values. Those get written directly into profile property values for each property ("column" in this case) defined.

This differs from the SQL sources because the spreadsheet is not contacted every time a profile is being recalculated.


Here is an example source plugin.ts file.

import { Initializer } from "actionhero";
import { plugin } from "@grouparoo/core";

import { test } from "./../lib/test";
import { connect } from "./../lib/connect";
import { disconnect } from "./../lib/disconnect";
import { exportProfile } from "../lib/export/exportProfile";
import { exportArrayProperties } from "../lib/export/exportArrayProperties";

import { getConnection as getTableConnection } from "../lib/table-import/connection";
import { getConnection as getQueryConnection } from "../lib/query-import/connection";

import { destinationOptions } from "../lib/export/destinationOptions";
import { destinationMappingOptions } from "../lib/export/destinationMappingOptions";

const packageJSON = require("./../../package.json");

export class Plugins extends Initializer {
  constructor() {
    super(); =;

  async initialize() {
      icon: "/public/@grouparoo/postgres/postgres.svg",
      apps: [
          name: "postgres",
          options: [
              key: "host",
              displayName: "Host",
              required: false,
              description: "The Postgres host.",
              placeholder: "localhost",
              key: "port",
              displayName: "Port",
              required: false,
              description: "The Postgres port.",
              placeholder: "5432",
              key: "database",
              displayName: "Database",
              required: true,
              description: "The Postgres database.",
              key: "schema",
              displayName: "Schema",
              required: false,
              description: "The Postgres schema (default: public).",
              placeholder: "public",
              key: "user",
              displayName: "User",
              required: false,
              description: "The Postgres user.",
              key: "password",
              displayName: "Password",
              required: false,
              description: "The Postgres user's password.",
              key: "ssl",
              displayName: "SSL",
              required: false,
                "Require the use of a SSL connection (default: false).  If you need custom SSL certificates paste in their values below.",
              key: "ssl_cert",
              displayName: "SSL Certificate",
              required: false,
              description: "The ssl certificate.",
              key: "ssl_key",
              displayName: "SSL Key",
              required: false,
              description: "The ssl certificate's key.",
              key: "ssl_ca",
              displayName: "SSL Certificate Authority",
              required: false,
              description: "The ssl certificate authority (CA).",
          methods: { test, connect, disconnect },
      connections: [getTableConnection(), getQueryConnection()],

  async start() {

Many SQL plugins use a helper from @grouparoo/app-templates to build the query and table sources. It helps standardize how things work across all the SQL types.

// table-import/connection
import { buildConnection } from "@grouparoo/app-templates/dist/source/table";
import { getSampleRows } from "./getSampleRows";
import { getColumns } from "./getColumns";
import { getTables } from "./getTables";
import { getChangedRows } from "./getChangedRows";
import { getPropertyValue } from "./getPropertyValue";
import { getPropertyValues } from "./getPropertyValues";
import { getChangedRowCount } from "./getChangedRowCount";

export function getConnection() {
  return buildConnection({
    app: "postgres",
    name: "postgres-table-import",
    description: "Import or update Profiles from a Postgres database table.",
    tableOptionDescription: "The table to scan",
// query-import/connection
import { buildConnection } from "@grouparoo/app-templates/dist/source/query";
import { executeQuery } from "./executeQuery";
import { getChangedRows } from "./getChangedRows";

export function getConnection() {
  return buildConnection({
    app: "postgres",
    name: "postgres-query-import",
    description: "Import or update Profiles via a custom Postgres query.",