Brad Ullery
It would be great for an automation to send a Web Hook (or HTTP Post). Ideally the message would include the record data so an API call is not required to get the record information.
But, at a minimum, the record id and the trigger detail would be useful to know if a record was created or updated.
Allowing a Solution Manager to create a custom webhook provides the ability to interact with virtually any REST-compliant API, opening up access to thousands of additional systems (even custom software APIs that are not publicly available). With support for inserting SmartSuite data into the outbound URL, parameters, header information and request body payload, SmartSuite can power complex integrations that support any type of workflow.
The addition of webhooks as triggers supports the reverse scenario - SmartSuite receiving data from any external system that supports outbound webhooks. Solution Managers will be able to create a custom URL for receipt of the webhook request, and then use any SmartSuite action to further process that data.
With an inbound webhook SmartSuite could receive data from custom internal applications that drive a business's core workflows. Team members would then be able to process that information inside of SmartSuite to complete their work, eliminating the need to create custom software or replacing dated or unintuitive interfaces.