TIBCO Scribe ® has built in support for Webhooks through our Event Solutions without requiring a specific Connector. Event Solutions provide a REST-based web service to allow access to TIBCO Scribe ® from outside sources. The first time you save a Message or Request/Reply Map in an Event Solution, TIBCO Scribe ® generates a unique Endpoint URL along with an access token.
Requet/Reply Maps are used primarily when the calling system needs a reply with data, however that is not an absolute requirement.
The request payload is defined in the TIBCO Scribe ® UI or via the Web API along with the required response to the calling system.
For example, assume you have a custom application and you want that application to add new leads to a Dynamics CRM account. With a Request/Reply Map, you can:
Design the schema for your input fields in the Wait For Request Block, such as the Name, Address, and Phone fields for the lead.
Define the schema for the fields you want returned in the Build Reply Block. In this example it might just be a Boolean value that says whether the lead was successfully created in Dynamics CRM.
Add the Endpoint URL generated in the Wait for Request Block to the part of your source code that sends the leads. The code for your custom application also requires a web request body that provides values for the fields you designed in the Wait for Request Block.
Write code in your custom application that parses the body of the web reply and retrieves any return values.
Using the Fast Connector Messaging Framework it is possible to setup a Connector which provides more options on format (JSON or XML) and also allows for manipulation of payload. Message Maps process asynchronously and are queued to for processing by the Agent, much like a “fire and forget” type of call.