← AWS + Ongage integrations

Ongage Find Subscriber with Ongage APIon New SNS Messages from AWS API

Pipedream makes it easy to connect APIs for Ongage, AWS and + other apps remarkably fast.

Trigger workflow on
New SNS Messages from the AWS API
Next, do this
Ongage Find Subscriber with the Ongage API
No credit card required
Trusted by 200,000+ developers from startups to Fortune 500 companies:
Trusted by 200,000+ developers from startups to Fortune 500 companies

Developers Pipedream

Getting Started

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

  1. Select this integration
  2. Configure the New SNS Messages trigger
    1. Connect your AWS account
    2. Select a AWS Region
    3. Configure SNS Topic Name
  3. Configure the Ongage Find Subscriber action
    1. Connect your Ongage account
    2. Configure Email Address
    3. Configure Halt on error?
  4. Deploy the workflow
  5. Send a test event to validate your setup
  6. Turn on the trigger

Details

This integration uses pre-built, open source 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

Description:Creates an SNS topic in your AWS account.Messages published to this topic are emitted from the Pipedream source.
Version:0.1.0
Key:aws-new-sns-messages

Trigger Code

const base = require("../common/sns");
const { toSingleLineString } = require("../common/utils");

module.exports = {
  ...base,
  key: "aws-new-sns-messages",
  name: "New SNS Messages",
  description: toSingleLineString(`
    Creates an SNS topic in your AWS account.
    Messages published to this topic are emitted from the Pipedream source.
  `),
  version: "0.1.0",
  dedupe: "unique", // Dedupe on SNS message ID
  props: {
    ...base.props,
    topic: {
      label: "SNS Topic Name",
      description: toSingleLineString(`
        **Pipedream will create an SNS topic with this name in your account**,
        converting it to a [valid SNS topic
        name](https://docs.aws.amazon.com/sns/latest/api/API_CreateTopic.html).
      `),
      type: "string",
    },
  },
  methods: {
    ...base.methods,
    getTopicName() {
      return this.convertNameToValidSNSTopicName(this.topic);
    },
  },
};

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.
LabelPropTypeDescription
AWSawsappThis component uses the AWS app.
N/Adb$.service.dbThis component uses $.service.db to maintain state between component invocations.
N/Ahttp$.interface.httpThis 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.
AWS RegionregionstringSelect a value from the drop down menu.
SNS Topic Nametopicstring

Pipedream will create an SNS topic with this name in your account,converting it to a valid SNS topicname.

Trigger Authentication

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

Follow the AWS Instructions for creating an IAM user with an associated access and secret key.

As a best practice, attach the minimum set of IAM permissions necessary to perform the specific task in Pipedream. If your workflow only needs to perform a single API call, you should create a user and associate an IAM group / policy with permission to do only that task. You can create as many linked AWS accounts in Pipedream as you'd like.

Once done, enter your access and secret key below.

About AWS

On-demand cloud computing platforms and APIs

Action

Description:Find a list subscriber in Ongage.
Version:0.0.1
Key:ongage-find-subscriber

Action Code

const ongage = require("../../ongage.app.js");

module.exports = {
  key: "ongage-find-subscriber",
  name: "Ongage Find Subscriber",
  description: "Find a list subscriber in Ongage.",
  version: "0.0.1",
  type: "action",
  props: {
    ongage,
    email: {
      propDefinition: [
        ongage,
        "email",
      ],
    },
    haltOnError: {
      propDefinition: [
        ongage,
        "haltOnError",
      ],
    },
  },
  async run () {
    try {
      return await this.ongage.findSubscriber(
        this.email,
      );
    } catch (err) {
      if (this.haltOnError) {
        throw err;
      }
      if (err.response) {
        return err.response.data;
      }
      return err;
    }
  },
};

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.

LabelPropTypeDescription
OngageongageappThis component uses the Ongage app.
Email Addressemailstring
Halt on error?haltOnErrorboolean

Action Authentication

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

Connect to your Ongage account using the Username and Password of the Ongage User who will be using and issuing the API commands, along with your Account Code, that you can find under the Account Profile. See docs.

x_username: your_ongage_username
x_password: your_ongage_password
x_account_code: your_ongage_account_code

About Ongage

Email Marketing Platform For Data-Driven Growth

More Ways to Connect Ongage + AWS

About Pipedream

Stop writing boilerplate code, struggling with authentication and managing infrastructure. Start connecting APIs with code-level control when you need it — and no code when you don't.

Into to Pipedream
Watch us build a workflow
Watch us build a workflow
4 min
Watch now ➜
"The past few weeks, I truly feel like the clichéd 10x engineer."
@heyellieday
Powerful features that scale
Manage concurrency and execution rate
Manage concurrency and execution rate

Queue up to 10,000 events per workfow and manage the concurrency and rate at which workflows are triggered.

Process large payloads up to 5 terabytes
Process large payloads up to 5 terabytes

Large file support enables you to trigger workflows with any data (e.g., large JSON files, images and videos) up to 5 terabytes.

Return custom responses to HTTP requests
Return custom responses to HTTP requests

Return any JSON-serializable response from an HTTP triggered workflow using $respond().

Use most npm packages
Use most npm packages

To use any npm package, just require() it -- there's no npm install or package.json required.

Maintain state between executions
Maintain state between executions

Use $checkpoint to save state in one workflow invocation and read it the next time your workflow runs.

Pass data between steps
Pass data between steps

Return data from any step to inspect it in a human-friendly way and reference the data in future steps via the steps object.