You should be able to use the same WebCoRE steps from the first post, but instead of posting to myjson.com, you would POST to a SharpTools Rule which has an HTTP Trigger:
So in my case, I created a new SharpTools rule with an HTTP Trigger and an action to copy the value that is received from WebCoRE into a SharpTools variable.
In this example, WebCoRE is sending over a variable called myValue
and I’m copying it into a SharpTools variable called $myText
.
Note that it’s completely optional to define the parameter name in the Trigger section, but sometimes it’s helpful almost as a form of documentation to yourself for what you’re expecting to receive.
Then I updated the existing WebCoRE piston and changed the ‘Method’ to POST and the URL to the HTTP Trigger URL for my new SharpTools Rule (make sure to save the SharpTools rule first so the HTTP trigger becomes active!).
As noted in the original post above, WebCoRE global variables use ‘@’ in their name and wont work, so if you are using global WebCoRE variables, copy those to a local WebCoRE variable to send across.