This is quite helpful for those who are not already aware of this. If you are integrating Salesforce with other systems using workflow and Salesforce’s native outbound message feature, how do you test the same. For example, you have configured the workflow rule and the outbound message and now you would want to make sure that when the workflow evaluation criteria and rule criteria is met, the outbound message is getting triggered. You may also want to know the format and the structure of the message that is being sent. This may be required by the team on the receiving side of the outbound message so that they know how to process it.
Ok, here is the trick. Navigate to URL https://requestb.in/ and click on ‘Create a RequestBin’. (Click on the images below to view in full screen)
This will give you a new Unique Bin URL. Copy the RequestBin Bin URL
Now all you need to do is in your outbound message endpoint use this RequestBin URL
And then execute a transaction that will cause the Workflow rule to fire and send the outbound message. One the outbound message is sent, switchback to the RequestBin browser window, refresh the page and you will see that the outbound message sent by Salesforce has landed here (the text highlighted in yellow below is the data that was sent from Salesforce based on the columns selected in outbound message definition)
Now, since RequestBin cannot return an acknowledgement back to Salesforce on the receipt of the outbound message, Salesforce will keep resending the outbound message for next 24 hours. So if you keep refreshing the RequestBin browser window, you will notice that the same message is landing again and again. If you want to stop Salesforce from resending the message again, then just delete the message from Outbound Message Queue in Salesforce.
Ain’t this useful?