https://github.com/elasticio/request-reply-component

Component for implementing Request-Reply pattern
https://github.com/elasticio/request-reply-component

component nodejs

Last synced: 3 days ago
JSON representation

Component for implementing Request-Reply pattern

• Host: GitHub
• URL: https://github.com/elasticio/request-reply-component
• Owner: elasticio
• Created: 2016-04-08T11:49:16.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2023-06-29T08:54:30.000Z (over 1 year ago)
• Last Synced: 2024-04-09T21:02:11.577Z (7 months ago)
• Topics: component, nodejs
• Language: JavaScript
• Homepage:
• Size: 418 KB
• Stars: 1
• Watchers: 11
• Forks: 2
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md

Awesome Lists containing this project

README

        
# HTTP Reply Component

## Table of Contents

* [Description](#description)

* [Actions](#actions)

  * [Reply](#reply)

  * [Reply With Attachment](#reply-with-attachment)

### Description

The component replies with messages to the client requested a webhook.

This component takes the incoming message body and applies the configured JSONata transformation on it, if present, and return a message back to the client requested a webhook of a given flow.

## Actions

### Reply

#### Configuration Fields

* **Custom HTTP Headers** - (string, optional): Provides with possibility to set additional headers separated by comma (e.g `Content-Language, User-Agent`)

#### Input Metadata

* **Content Type (Defaults to 'application/json')** - (string, optional, defaults to `application/json`): Header value tells the client what the content type of the returned content actually is.

* **Response Body** - (string/Object, required): Body to send as the response

* **Response Status Code** - (number, optional, defaults to `200`): Integer number between `200` and `999` (more info about status codes in [rfc7231](https://datatracker.ietf.org/doc/html/rfc7231#section-6) standart)

If provided `Custom HTTP Headers` there will be additional field:

* **customHeaders**, contains:

  * **Header ** - you can provide value to your custom header here

#### Output Metadata

Same as `Input Metadata`

### Reply With Attachment

#### Configuration Fields

* **Custom HTTP Headers** - (string, optional): Provides with possibility to set additional headers separated by comma (e.g `Content-Language, User-Agent`)

#### Input Metadata

* **Content Type (Defaults to 'application/json')** - (string, optional, defaults to `application/json`): Header value tells the client what the content type of the returned content actually is.

* **Attachment URL** - (string, required): Link to file (on platform or external) that will be used as response

* **Response Status Code** - (number, optional, defaults to `200`): Integer number between `200` and `999` (more info about status codes in [rfc7231](https://datatracker.ietf.org/doc/html/rfc7231#section-6) standart)

If provided `Custom HTTP Headers` there will be additional field:

* **customHeaders**, contains:

  * **Header ** - you can provide value to your custom header here

#### Output Metadata

Same as `Input Metadata`