Events Overview

The Axway AMPLIFY Events Framework provides a uniform mechanism for subscribing to events from API providers like Salesforce, HubSpot, QuickBooks, and Dropbox. Our Events Framework gives you the flexibility to receive notifications to your app regarding user activity by having our connectors subscribe to API provider events. API providers publish changes to notify the connectors that events have occurred. 

For example, a user creates an event (for example, create/update/delete a file) to their Dropbox account using the Dropbox user interface. This event will generate a notification that will be published to your Dropbox connector. The notification will include as default some of our Axway AMPLIFY-standardized fields as objectType, objectId, eventType, elementKey, and so forth while from the vendor, the user could have additional information like name, path, size, and so forth. An Event Notification can contain up to 10 (for polling) or 20 (for webhook) events objects inside depending on the vendor response. 

In the context of events-triggered flows, only a single event object can be referenced from the trigger event, even if the event may have been part of a larger event notification. After the notification of the event, the Dropbox connector notifies your app that a new file has been uploaded. Your app can then be updated with the most current data making it that much more cooperative and powerful.

Event Configuration Types

Axway AMPLIFY currently supports building integrations with polling or webhooks capability.

With Polling, Axway AMPLIFY executes a configured query every n minutes and captures the changed information.

With Webhooks, the API provider lets Axway AMPLIFY know what information has changed. Some API providers require some additional configuration setup for Event Management. Instructions and screenshots for these configurations can be found in the Connector Guides under Events for each API provider.

Receiving Events

Events can be sent to your application by setting the Event Notification Callback URL (event.notification.callback.url) configuration value to your application's URL during provisioning, such as . You can also return events to the connectors with an Event Notification Callback URL like<Connector-Key>/.

To update an active instance use the PATCH /instances or PATCH /instances/{id}/configuration/{configurationId} endpoints to add an Event Notification Callback URL.

Related Links