Firestore Collection Query with multiple filters : Value for argument "value" is not a valid ...
I would like to filter collection with multiple filters 😄
"Value for argument "value" is not a valid query constraint. Cannot use "undefined" as a Firestore value. If you want to ignore undefined values, enable
ignoreUndefinedProperties."...Solution:
Hi @Link, the
object validation node's result here will be false (you can confirm by clicking the green arrow icon). As in Body you are giving an Object but it only accepts and validates object. Due to which in the second node Firestore Collection Query, the value you are referencing from body is breaking (invalid),
To fix this, either pass the body as a valid object.
```{...
API header error
I'm trying to make an API call to OpenAI's list messages API.
I keep getting the error saying I must provide the header, which I did in the test. There are no options in the node to place the header....
Solution:
Hi @Ada, does the API header requires a special key or is it just a simple Authorization hearder? If it requires a special key, then you'll be require to modify the code logic a bit before providing the custom header directly to make this work.
Consider this example of Rapid API with custom header:
You can add the key and host directly like this by modifying the headers in the code of the API call node. Ensure to pass their values in the export params and node fields too to make it work.
...
I can't get BuildShip Trigger to Work.
Hey there, i am currently trying to work out how to get the buildshipt tirgger to work. I made two worflows for test purposes. One that has the trigger and simply just is supposed to return a string. The other one should just execute the trigger and return the string. I left the data object empty.
Both workflows are "shipped", project id is correct. From tests and logs i was able to gather the following information:
1. trigger exits with error "Fetch Failed"
2. logging the error returns "src property must be a valid json object"
3. the fetch itself seems to work, because not calling it asynchornus returns success but without any return data....
API Key
Hello, I am building a web3 app, and I would like to integrate buildship with Moralis API .
But I wonder How to input the API Key inside buildship, is it not in the secret key section? When I input the API key in the authorization, it returns this:
{
"status": 401,...
Issues with Loop node :c
I am having this error with my flow. I want to get the comments from my posts on my Facebook page, but since it's not possible to get them directly, what I am trying to do first is make an HTTP request to the Meta API to get all the post IDs (in an array) from my Facebook page. Then, I use those IDs to get the comments from each post. Up to this point, it works correctly.
Then, I also have a JSON of several objects:
{...
I need help with "BuildShip Trigger & Execute Workflow Nodes" - (Not working)
I am trying to use the BuildShip Trigger & Execute Workflow Nodes to create and update Firestore documents, but they're not responsive for some reason.
I keep getting the error message:
{...
Solution:
One quick thing to check... you must ship the workflow you're trying to trigger (the one with the BuildShip Trigger) before you test it out with the Execute Workflow node.
No API endpoint after deploying
Hey guys, I seem to be running into an issue where I'm not getting my API endpoint after shipping, any ideas as to why?
Cheers!...
Solution:
Hi @adamsardo You can click the link icon to get the endpoint.
email trigger
Hi nocoders, currently I'm having an issue with the email trigger; I've been trying to get the attachment but with no success. I already get the json using:
${(x)body.fields[attachment-info]}
Do you have any idea how to access to: attachment1 > filename ?...Solution:
Hi @Zarcco, extract the data received from the response of the which you require to an empty script node and then edit the node with the AI to with prompt extract the require data from this json, give the above json as example in the prompt as well.
For using with the dot notation, you'll be require to add
email variable instead from body, as the body you are referencing it from the request not from the Email Trigger request body. Use this expression. Please note you might encounter while adding this expression in editor, we'll are tracking and will add a fix soon....