Return HTTP Response with HTTP / Webhook API on New Webhook Event (Instant) from Payhere API

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

Trigger workflow on

New Webhook Event (Instant) from the Payhere API

Next, do this

Return HTTP Response with the HTTP / Webhook 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 Payhere trigger and HTTP / Webhook action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Webhook Event (Instant) trigger
1. Connect your Payhere account
2. Configure Integration Name
3. Select a Event Type
Configure the Return HTTP Response action
1. Connect your HTTP / Webhook account
2. Configure Response Status Code
3. Optional- Configure Response Headers
4. Optional- Configure Response Body
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 Webhook Event (Instant) on Payhere

Description:Emit new event for each new webhook event

Version:0.0.1

Key:payhere-new-webhook-event

View on GitHub

Payhere Overview#

Payhere, powered by Xendit, offers a powerful API that allows you to craft seamless payment experiences within your apps and websites. By leveraging this API on Pipedream, you can automate payment processing, synchronize transaction data with accounting systems, or trigger communication based on payment events. Pipedream's serverless platform enables the orchestration of Payhere with an array of other services to streamline financial operations, enhance customer engagement, and maintain robust financial records.

Trigger Code#

import payhere from "../../payhere.app.mjs";
import constants from "../common/constants.mjs";

export default {
  key: "payhere-new-webhook-event",
  name: "New Webhook Event (Instant)",
  description: "Emit new event for each new webhook event",
  type: "source",
  version: "0.0.1",
  dedupe: "unique",
  props: {
    payhere,
    db: "$.service.db",
    http: "$.interface.http",
    integrationName: {
      label: "Integration Name",
      description: "Friendly name of your platform, helps with metrics and debugging",
      type: "string",
    },
    resource: {
      label: "Event Type",
      description: "The event that will be listen",
      type: "string",
      options: constants.WEBHOOK_EVENT_TYPES,
    },
  },
  methods: {
    _getWebhookId() {
      return this.db.get("webhookId");
    },
    _setWebhookId(webhookId) {
      this.db.set("webhookId", webhookId);
    },
  },
  hooks: {
    async activate() {
      const response = await this.payhere.createWebhook({
        integration: this.integrationName,
        post_url: this.http.endpoint,
        resource: this.resource,
      });

      this._setWebhookId(response.id);
    },
    async deactivate() {
      const webhookId = this._getWebhookId();
      await this.payhere.removeWebhook(webhookId);
    },
  },
  async run(event) {
    const { body } = event;

    const resourceId = body?.payment?.id ?? body?.subscription?.id;
    const ts = body?.payment?.created_at ?? body?.subscription?.created_at;

    this.$emit(body, {
      id: resourceId,
      summary: `New event ${body.event} with id ${resourceId}`,
      ts: Date.parse(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
Payhere	`payhere`	`app`	This component uses the Payhere app.
N/A	`db`	`$.service.db`	This component uses `$.service.db` to maintain state between executions.
N/A	`http`	`$.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.
Integration Name	`integrationName`	`string`	Friendly name of your platform, helps with metrics and debugging
Event Type	`resource`	`string`	Select a value from the drop down menu:`{ "label": "Payment Received", "value": "payment_received" }{ "label": "Subscription Cancelled", "value": "subscription_cancelled" }{ "label": "Subscription Created", "value": "subscription_created" }`

Trigger Authentication#

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

You can find your API key in the integrations section of the merchants admin.

For environment, Payhere provides a sandbox site so you can easily test your integration without using your own money. See docs. If you aren't testing, use the production option.

About Payhere#

Easy payment links

Action#

Return HTTP Response on HTTP / Webhook

Description:Use with an HTTP trigger that uses "Return a custom response from your workflow" as its `HTTP Response`

Version:0.0.3

Key:http-return-http-response

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.

Action Code#

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

export default {
  key: "http-return-http-response",
  name: "Return HTTP Response",
  description:
    "Use with an HTTP trigger that uses \"Return a custom response from your workflow\" as its `HTTP Response`",
  type: "action",
  version: "0.0.3",
  props: {
    http,
    resStatusCode: {
      type: "integer",
      label: "Response Status Code",
      description:
        "The [status code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status) to return in the HTTP response.",
      default: 200,
      min: 100,
      max: 599,
    },
    resHeaders: {
      type: "object",
      label: "Response Headers",
      description: "The headers to return in the HTTP response.",
      optional: true,
    },
    resBody: {
      type: "any",
      label: "Response Body",
      description: "The body to return in the HTTP response.",
      optional: true,
      default: "{ \"success\": true }",
    },
  },
  async run({ $ }) {
    const status = this.resStatusCode;
    await $.respond({
      status,
      headers: this.resHeaders,
      body: this.resBody,
    });
    $.export("$summary", `Responded successfully with status ${status}`);
  },
};

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
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.
Response Status Code	`resStatusCode`	`integer`	The status code to return in the HTTP response.
Response Headers	`resHeaders`	`object`	The headers to return in the HTTP response.
Response Body	`resBody`	`any`	The body to return in the HTTP response.

Action Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

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

More Ways to Connect HTTP / Webhook + Payhere#

Other Popular Integrations#

Send any HTTP Request with HTTP / Webhook API on New Webhook Event (Instant) from Payhere API

Payhere + HTTP / Webhook

Try it

Send GET Request with HTTP / Webhook API on New Webhook Event (Instant) from Payhere API

Payhere + HTTP / Webhook

Try it

Send POST Request with HTTP / Webhook API on New Webhook Event (Instant) from Payhere API

Payhere + HTTP / Webhook

Try it

Send PUT Request with HTTP / Webhook API on New Webhook Event (Instant) from Payhere API

Payhere + HTTP / Webhook

Try it

Validate Webhook Auth with HTTP / Webhook API on New Webhook Event (Instant) from Payhere API

Payhere + HTTP / Webhook

Try it

Popular Triggers#

New Webhook Event (Instant) from the Payhere API

Emit new event for each new webhook event

Try it

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