Loading Profile...
Sending to Yahoo! Pipes
Please make it easier for me to send information to a Yahoo! Pipe for processing before continuing with the workflow. At the moment, the REST module is cool, but the JSON format doesn't get handled by Pipes well.
I’m looking forward to better days
2
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The company has this under consideration.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?To be more specific, when you send to Pipes, it interprets the 'data=...' as a string, not as JSON. It sucks to deal with this. Please make this easier. -
Inappropriate?Thanks for the feedback Jonathan,
Which module are you using inside Yahoo! Pipes to receive the call from tarpipe? -
Inappropriate?Hey Bruno!
What I'm doing is capturing the 'data' parameter that's POSTed to Pipes by declaring it as a user input and using the 'item builder' to assign that to the 'content' property of an item.
The problem is that the data POSTed from tarpipe is sent as JSON, which is just read in as a string in the pipe, so your 'content' property ends up with a messy JSON string as its value.
I've knocked up a test pipe and workflow so you can see how this works. Send an email to ably39hoys@tarpipe.net - this goes through the workflow with ID 3ded214ccd3991d9664abf6335dc49fd and through the Yahoo! Pipe at http://pipes.yahoo.com/jayfresh/fromt... - the pipe POSTs whatever it has been sent to http://postin.appjet.net, where you'll be able to see how pipes encoded the data sent from appjet.
This is a screenshot of http://postin.appjet.net showing what I'm talking about:
http://img.skitch.com/20090604-r333ja...
I’m thinking this is more complicated than it should be
-
Inappropriate?Thanks for the feedback Jonathan,
I'm not sure I completely understand what you're trying to do.
I tried myself POSTing directly to http://postin.appjet.net and what I see there is my data as text — I think you need to transform the JSON string into an object on your side to be able to use it.
I'd be willing to help you further but I don't know the details of appjet or what exactly you're trying to do. -
Inappropriate?Hi Bruno,
Sorry my examples were not very clear!
What I am trying to do is use Yahoo! Pipes as an intermediate step in my tarpipe workflow to process the email text that comes into the workflow.
Do you have any ideas how I could do this?
My complaint was that using the REST block in tarpipe is not very useful for POSTing to a Yahoo! Pipe.
J.
I’m hoping this helps
-
Inappropriate?Hi Jonathan,
The tarpipe REST connector is meant to be compatible with the Yahoo! Pipes Web Service Module (see http://pipes.yahoo.com/pipes/docs?doc...), not with what Yahoo! Pipes accepts information from the outside.
Yahoo! Pipes accepts input as simple text. What tarpipe is sending is very similar to what the Pipes Web Service Module is sending out, and yes, it is text (JSON encoded).
So, I think you can explore Pipes string manipulation operators and see if you can extract the information you want from what tarpipe is sending.
Or, you could do it yourself on your final script.
Thanks again for the great feedback and I hope you can make it work.
1 person thinks
this is one of the best points
-
Inappropriate?Thanks Bruno, I'll have a go making a pipe that chops out the information. It would be a lot easier to have an option on the REST block so it just POSTed form-encoded key/value pairs.
tite=this&description=that
What do you think?
J.
I’m speculative
-
Inappropriate?Jonathan,
Absolutely. That's something that we also thought about but we'll have to wait a little longer.
Thanks -
Inappropriate?Hey Bruno,
I had a go at making a Pipe that works for me. I can do the string parsing to get at the information in the JSON-encoded string. The next problem is sending the information back to tarpipe...
According to this blog post - http://www.pipetree.com/qmacro/blog/2... - the REST connector expects data back as a string like so:
{
"items":[
{
"title": "The response!",
"description": "Long text description of the response",
"link": "http://example.org/banana/"
}
]
}
This is inconsistent with the JSON output format used by Yahoo! Pipes (which you seem to want to be consistent with given your previous comments), which looks like this:
{
"count":1,
"value": {
"title":"convert from tarpipe (description only)",
"description":"Pipes Output",
"link":"http:\/\/pipes.yahoo.com\/pipes\/pipe.info?_id=lAUEoB1R3hGTqt6hggSecQ",
"pubDate":"Thu, 04 Jun 2009 15:44:32 +0000",
"generator":"http:\/\/pipes.yahoo.com\/pipes\/",
"callback":"",
"items":[{
"title":"converted from tarpipe",
"description":"Any description"
}]
}
}
The important difference is that the 'items' array is contained in the 'value' object, not the root object.
Thoughts?
J.
I’m not happy with this apparent inconsistency
1 Comment Add a comment
This is one of the best points
-
Sorry about the whitespace not working out - I had put tabs in! -
Inappropriate?Hi Jonathan,
The REST connector is compatible with the Yahoo! Pipes Web Service Module (http://pipes.yahoo.com/pipes/docs?doc...), not with Yahoo! Pipes itself.
We made it that way so that Web services that are currently already working with the Yahoo! Pipes Web Service Module can also work with tarpipe without changing anything.
1 person thinks
this is one of the best points
-
Inappropriate?Yes indeed! I realised that shortly after I'd posted, so apologies for my own confusion.
I’m resolved (a bit)
-
Inappropriate?Hey Bruno,
Ok, I've made a proxy that sits between tarpipe and Yahoo! Pipes and handles the conversion of data formats. It's here: http://tarpipe-yahoo_pipes_proxy.jgat...
You use it as the serviceURL for a REST connector. It needs a parameter ?pipeId=someYahooPipeID on the end, where this points to the pipe that is going to do the processing.
If you take a look at the tarpipe workflow with ID 931a3b4c89f1a16a73ce370d114b266f you can see this in action.
An example (very simple) Yahoo! Pipe is at:
http://pipes.yahoo.com/pipes/pipe.inf...
How's that?
J.
I’m pretty excited by the possibilities
-
EMPLOYEE
