V8.1 Feature Request

[bkonia]

As I mentioned to Vlad, my wishlist for REST consumption consists of the following items:

• Choice of using GET or POST
• If using POST, the ability to send a standard POST request or JSON.
• Ability to specify custom headers in the request.
• Receive the response in one of the following formats:
  • Simple text value, which can be mapped to an attribute.
  • String containing name/value pairs, which can be mapped to the attributes specified by the keys, in a single BO.
  • JSON, mapped to a BO hierarchy, as described in my prior post.
  • XML mapped to a BO hierarchy.

[PointsWell]

Added to wish list board

[ACDC]

As I mentioned to Vlad, my wishlist for REST consumption consists of the following items:

Choice of using GET or POST
If using POST, the ability to send a standard POST request or JSON.
Ability to specify custom headers in the request.
Receive the response in one of the following formats:
Simple text value, which can be mapped to an attribute.
String containing name/value pairs, which can be mapped to the attributes specified by the keys, in a single BO.
JSON, mapped to a BO hierarchy, as described in my prior post.
XML mapped to a BO hierarchy.

Sometimes, the only way to make a wish come true is to pay for it .
I would gladly commit to a custom plug-in of some sort that could bring this functionality forward

Are there any other volunteers and someone who can write the spec and submit to support for a quote on getting this done

[bkonia]

Actually, Vlad has informed me that this is on the roadmap for 8.1. I'm not sure if they intend to do the complete feature set I listed here, but at least some of this functionality should be implemented.

[tford]

Brad,

Do you know if the functionality described above which you say should be in 8.1 would theoretically have the ability to receive Webhooks from SendGrid or Mandrill as described here:

SendGrid: https://sendgrid.com/docs/API_Reference ... index.html
Mandrill: https://mandrill.zendesk.com/hc/en-us/a ... o-Webhooks

The also would impact Ben's request at: https://www.awareim.com/forum/viewtopic.php?f=1&t=9731

That would be HUGE if 8.1 would make webhooks configurable in the Configuration Tool. It would substantially extend the email functionality to include great info about how & when a recipient interacts with an email sent by AwareIM. When paired with additional AwareIM processing rules, a user could trigger other workflow steps based on the webhook info received.

[BenHayat]

Brad,

Do you know if the functionality described above which you say should be in 8.1 would theoretically have the ability to receive Webhooks from SendGrid or Mandrill as described here:

SendGrid: https://sendgrid.com/docs/API_Reference ... index.html
Mandrill: https://mandrill.zendesk.com/hc/en-us/a ... o-Webhooks

The also would impact Ben's request at: https://www.awareim.com/forum/viewtopic.php?f=1&t=9731

That would be HUGE if 8.1 would make webhooks configurable in the Configuration Tool. It would substantially extend the email functionality to include great info about how & when a recipient interacts with an email sent by AwareIM. When paired with additional AwareIM processing rules, a user could trigger other workflow steps based on the webhook info received.

Exactly Tom. Having REST communications, allows us to communicate with mail server in two way fashion, so we know if mail was delivered or not and etc. The SMTP route, you have no way to know and in critical situations where email delivery is critical.

[johntalbott]

Ain't no REST for the wicked.

[bkonia]

Do you know if the functionality described above which you say should be in 8.1 would theoretically have the ability to receive Webhooks from SendGrid or Mandrill as described here:

Hi Tom,

I reviewed the Sendgrid and Mandrill docs. Most of this functionality is already supported by the AIM REST service. The problem is, the REST service only supports GET requests, not POST requests and these web hooks require POST, more specifically JSON POST. The main difference between GET and POST is with a GET, the entire request is encoded within the URL parameters. With a POST, it's encoded within the request body, which allows for sending a lot more data.

It would be simple for the AIM development team to add support for POST and JSON POST requests in the REST service. The POST parameters or the JSON object would be mapped to attributes in exactly the same way as the GET parameters. When creating a REST service, the developer would specify whether he wants the service to receive the data in GET, POST or JSON POST format. Hopefully, if enough people chime in, they'll be encouraged to implement this.

[RLJB]

I think Brad has described a perfect method in his last forum post on Page 2, consuming a restful API in such a manner would be great.

+1

[ACDC]

not POST requests and these web hooks require POST,

If you set up the Sendgrid POST webhook event to use your URL configured as follows:

"http://localhost:8080/logonOp.awsp?doma ... lue3...etc etc"

I have used this before to capture web hooks. Once you have setup an Object for Sendgrid and the relevant Sendgrid event attributes and a User so the webhook can log in it works perfectly

[bkonia]

I have used this before to capture web hooks. Once you have setup an Object for Sendgrid and the relevant Sendgrid event attributes and a User so the webhook can log in it works perfectly

I assume you're referring to web hooks in general, not SendGrid specifically, because this will definitely NOT work with SendGrid. The SendGrid web hook communicates via POST, not GET and the data structures are sent as JSON objects, not as query string parameters. Thus, you will receive a notification, but there will be no way to parse the data from the notification.