Smart Event Not Working

[Ember Robb]

Hello,

I'm in the process of setting up smart events for the first time in Sage Intacct. I am trying to send some data through an event. For testing, I created an event to send anytime a timesheet entry is created, deleted, approved, or declined.

Here is what my event looks like:

 

I've followed the example here: https://www.intacct.com/ia/docs/en_US/help_action/Default.htm#cshid=HTTP_post_Smart_Event

I am able to send data to this URL; I tested in in Postman and it works. However, nothing happens when I create a timesheet in Sage. I expect to see a message in my API logs, but no such thing happens.

Can anyone offer guidance in regards to what I am missing here or doing wrong?

Thanks,

Ember

[Josh Kenzer]

Stab in the dark here, but Smart Events only fire on posting, not on saving as draft. Could that be it?

[Ember Robb]

I am specifically posting and not saving as draft. Thanks for the idea, though. Appreciate it.

 

Edited August 23 by Ember Robb

[Sterio, Louis]

@Ember Robb I have a personal AWS web server and I setup the same smart event that you defined except I pointed to my endpoint.

My endpoint logs the request into an output file. This is working without issues for me. Also you can check the smart event log under Company > Admin > Smart Event jobs to see the status of your job.

 

[Ember Robb]

Thanks @Sterio, Louis

This is the error that comes up in Sage:


I spoke with IT and they think it might be a problem with Sage not liking our non-standard port number. 

[Sterio, Louis]

This is most likely the case

[Ember Robb]

We resolved this issue by removing our non-standard port. Thanks for the help everyone.

[Lee Savidge]

Just looked at this. Two things. When sending arguments to the HTTP Post end point, you don't need to separate them with an &. You can just put them in a long list like this:

sessionid={!USERPROFILE.SESSIONID!}
endpoint={!API_ENDPOINT!}
useremail={!USERPROFILE.EMAIL!}
 

Smart events and triggers are limited to using port 80 or port 443 only. I raised a support case about this a while ago and got that response. It is annoying especially if you have multiple site configured and port 443 is already being used by something and you can't share it.