Integrate Enmeshed

Since the Connector is based on the Runtime, all Modules of the Runtime are also available in the Connector.

Additionally, the Connector defines its own Modules that only make sense in the context of a Connector and are therefore not defined in the Runtime.

Read more about the Module configuration on the icon in each title.

AMQP Publisher

This Module proxies all events in the internal event bus of the Connector to an exchange in a configurable AMQP server.

Compared to webhooks, this gives you the full feature set of a message broker. There are multiple scenarios where this Module outweighs the Webhooks Module. For example:

  • You need persistence for the triggered events.
  • You want to integrate Enmeshed into an already existing message broker.

Auto Accept Relationship Creation Changes

It is not recommended to use this Module for production scenarios.

The autoAcceptRelationshipCreationChanges Module listens to the events about incoming Relationship Change Requests. It immediately accepts the Requests, using the configured responseContent.

Keep in mind that you need to synchronize the state of the Connector with the Backbone in order to receive incoming Relationship Requests. The sync Module automates this, but you can also do this manually by calling the /api/v2/Account/Sync route.

Core HTTP API

This Module contains the HTTP API with all Enmeshed base functionalities.

Sync

The sync Module regularly fetches changes from the Backbone (e.g. new Messages / new incoming Relationship Requests). This process automatically triggers the events used by other Modules like the webhooks Module.

WebhooksV2

With the REST API, pull mechanisms are supported. However, as there are many bidirectional scenarios within Enmeshed, a push mechanism is favorable: the Connector is synchronizing its state with the Backbone and notifies the organization’s backend services about changes.

For this, the Connector supports the configuration of webhooks which are called every time a specific Connector Event is triggered (e.g. a new Message has been received => transport.messageReceived).

Keep in mind that you need to synchronize the state of the Connector with the Backbone in order to receive events. The sync Module automates this, but you can also do this manually by calling the /api/v2/Account/Sync route.

Updated: