Send Transactional Email with SARE API on New Requests (Payload Only) from HTTP / Webhook API

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

Trigger workflow on

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

Next, do this

Send Transactional Email with the SARE 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 SARE action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the Send Transactional Email action
1. Connect your SARE account
2. Configure Email
3. Configure Subject
4. Configure From
5. Optional- Select a Newsletter Type
6. Optional- Select a Newsletter
7. Optional- Configure HTML
8. Optional- Configure TXT
9. Optional- Configure Encoding
10. Optional- Configure Reply To
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 Requests (Payload Only) on HTTP / Webhook

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

Version:0.1.1

Key:http-new-requests-payload-only

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";

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

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
N/A	`httpInterface`	`$.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.
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

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#

Send Transactional Email on SARE

Description:Send a transactional email. [See the documentation](https://dev.sare.pl/rest-api/other/index.html#post-/send/mail/transactional)

Version:0.0.1

Key:sare-send-email

View on GitHub

SARE Overview#

The SARE API provides robust tools for email marketing and automation, enabling users to manage subscribers, send emails, and analyze campaigns directly via API. By leveraging SARE's features on Pipedream, you can automate workflows involving email operations, integrate with other platforms for enhanced data handling and customer engagement, and streamline communications in various marketing campaigns. This integration can particularly benefit marketers looking to automate responses based on subscriber behavior or integrate email marketing metrics with other business tools.

Action Code#

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

export default {
  key: "sare-send-email",
  name: "Send Transactional Email",
  description: "Send a transactional email. [See the documentation](https://dev.sare.pl/rest-api/other/index.html#post-/send/mail/transactional)",
  version: "0.0.1",
  type: "action",
  props: {
    sare,
    email: {
      propDefinition: [
        sare,
        "email",
      ],
    },
    subject: {
      propDefinition: [
        sare,
        "subject",
      ],
    },
    from: {
      propDefinition: [
        sare,
        "from",
      ],
    },
    newsletterType: {
      type: "string",
      label: "Newsletter Type",
      description: "The type of the newsletter you want to send.",
      optional: true,
      options: [
        "ready",
        "temporary",
      ],
    },
    newsletter: {
      propDefinition: [
        sare,
        "newsletter",
        ({ newsletterType }) => ({
          newsletterType,
        }),
      ],
      optional: true,
    },
    html: {
      type: "string",
      label: "HTML",
      description: "Message content in html format.",
      optional: true,
    },
    txt: {
      type: "string",
      label: "TXT",
      description: "Message content in text format.",
      optional: true,
    },
    encoding: {
      type: "string",
      label: "Encoding",
      description: "Coding of the sent newsletter. The coding must be consistent with those available in the system.",
      optional: true,
    },
    replyto: {
      type: "string",
      label: "Reply To",
      description: "Reply-To field for shipping. The value should be a syntactically valid email address.",
      optional: true,
    },
  },
  async run({ $ }) {
    if ((!this.newsletter) && (!this.html) && (!this.txt)) {
      throw new ConfigurationError("You must provide at least **Newsletter**, **HTML** or **TXT**.");
    }

    const response = await this.sare.sendTransactionalEmail({
      $,
      data: [
        {
          email: this.email,
          subject: this.subject,
          from: this.from,
          newsletter: this.newsletter,
          html: this.html,
          txt: this.txt,
          encoding: this.encoding,
          replyto: this.replyto,
        },
      ],
    });
    $.export("$summary", `Successfully sent email to ${this.email}`);
    return response;
  },
};

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
SARE	`sare`	`app`	This component uses the SARE app.
Email	`email`	`string`	The email address of the subscriber.
Subject	`subject`	`string`	The subject of the transactional email.
From	`from`	`string`	The sender email address.
Newsletter Type	`newsletterType`	`string`	Select a value from the drop down menu:`readytemporary`
Newsletter	`newsletter`	`integer`	Select a value from the drop down menu.
HTML	`html`	`string`	Message content in html format.
TXT	`txt`	`string`	Message content in text format.
Encoding	`encoding`	`string`	Coding of the sent newsletter. The coding must be consistent with those available in the system.
Reply To	`replyto`	`string`	Reply-To field for shipping. The value should be a syntactically valid email address.

Action Authentication#

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

About SARE#

Omnichannel Marketing, Marketing automation.

More Ways to Connect SARE + HTTP / Webhook#

Other Popular Integrations#

Add Email with SARE API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + SARE

Try it

Add Email with SARE API on New Requests from HTTP / Webhook API

HTTP / Webhook + SARE

Try it

Remove Email from Groups with SARE API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + SARE

Try it

Remove Email from Groups with SARE API on New Requests from HTTP / Webhook API

HTTP / Webhook + SARE

Try it

Send Transactional Email with SARE API on New Requests from HTTP / Webhook API

HTTP / Webhook + SARE

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