-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PostAgent and XMLRPC - howto? #1361
Comments
Hi @nata-lee, I've never actually used true XML-RPC. (As opposed to ajax, which is usually JSON these days.) You may want to have Huginn post to a server that logs your requests, to make sure they look right. http://requestb.in/ could be useful here. |
Hi @cantino, thank you for the answer.
I just need an example. |
The following JSON options are pretty close: {
"post_url": "http://requestb.in/123456",
"expected_receive_period_in_days": "1",
"content_type": "xml",
"method": "post",
"payload": {
"methodName": "examples.getStateName",
"params": [
{
"value": {
"i4": "41"
}
}
]
},
"headers": {},
"emit_events": "false",
"xml_root": "methodCall"
} When pointing at a requestbin I made, I got this: |
@cantino I think the problem is the |
Wait, what's the problem? Isn't might output what @nata-lee is looking for? |
@dsander is quite right. I can't get multiple
is impossible via huginn interface :( Or I don't know how to get it, so I asked my question. |
I don't think that is possible at the moment, but I am planning to change the PostAgent to allow sending arbitrary data which can be formatted using liquid. |
When `content_type` contains a MIME type and `payload` is not a Hash the string in `payload` will be send as the HTTP body and `content_type` is send as the `Content-Type` header. huginn#1361
When `content_type` contains a MIME type and `payload` is not a Hash the string in `payload` will be send as the HTTP body and `content_type` is send as the `Content-Type` header. huginn#1361
I don't think that will ever be possible with the way Please feel free to reopen if you need further assistance! |
Hello!
Huginn makes my life easier, but some times I'm confused.
I'd like to use xml-rpc with the PostAgent. Specification here: http://xmlrpc.scripting.com/spec.html
But I can't build the sctucture with multiple parameters with the same name. Huginn doesn't let me do this, it's always a json error.
My agent:
{ "post_url": "http://domain/xmlrpc.php", "expected_receive_period_in_days": "1", "content_type": "xml", "method": "post", "no_merge": "true", "xml_root": "methodCall", "payload": { "methodName": "wp.newPost", "params": { "param": { "value": "1" } } }, "headers": {}, "emit_events": "false" }
I need more and multible but how? What am I doing wrong?
Could you help me?
The text was updated successfully, but these errors were encountered: