Christopher30
BBuildShip
•Created by jeff_sss on 11/20/2024 in #❓・buildship-help
Cannot Deploy/Ship via Flow Builder 2.0
I can confirm that a branch node is working correctly now (I tried it on a new workflow).
43 replies
BBuildShip
•Created by jeff_sss on 11/20/2024 in #❓・buildship-help
Cannot Deploy/Ship via Flow Builder 2.0
Hi @Gaurav Chadha , Good news—I tried again today to add the "Postgres Fetch Table Data" node and deploy the workflow. It finally worked, and I was able to ship the workflow!
Hopefully, it wasn't just a one-time thing and it will also work in the future.
43 replies
BBuildShip
•Created by jeff_sss on 11/20/2024 in #❓・buildship-help
Cannot Deploy/Ship via Flow Builder 2.0
I will record it tomorrow @Gaurav Chadha
Btw, I also submitted the ticket earlier this week mentioning the same error that @jeff_sss is talking about - the condition on the branch node was true, but the workflow executed (in test mode) the "else" branch side.
43 replies
BBuildShip
•Created by jeff_sss on 11/20/2024 in #❓・buildship-help
Cannot Deploy/Ship via Flow Builder 2.0
Are there any updates about your situation @jeff_sss?
43 replies
BBuildShip
•Created by Mike on 11/24/2024 in #❓・buildship-help
Unclear workflow ship failure error
I don't think it is the trigger that is causing the issue @Mike
I have a similar problem, and I am using the Rest API trigger. Another user @Nayls also had a similar problem but was using a scheduled trigger.
My flow was not migrated, I have tried multiple times to create a new flow and then to add a Postgres Fetch Table Data node, but it fails to ship the flow every time. (it is possible to ship the workflow if instead I add a Postgres Insert Data node)
9 replies
BBuildShip
•Created by jeff_sss on 11/20/2024 in #❓・buildship-help
Cannot Deploy/Ship via Flow Builder 2.0
@Gaurav Chadha I have not only tried to delete and add the node again, but I also have tried to start a new workflow, it still gives the same error.
43 replies
BBuildShip
•Created by jeff_sss on 11/20/2024 in #❓・buildship-help
Cannot Deploy/Ship via Flow Builder 2.0
@Gaurav Chadha It is a flow built on V2. + The Postgres node is not edited and it works in test mode, but deployment fails.
One thing to mention - last week when I was doing my account's migration to V2, it first showed that the migration failed, but the whole system was still updated to v2 and the new functionality was ready for using.
43 replies
BBuildShip
•Created by jeff_sss on 11/20/2024 in #❓・buildship-help
Cannot Deploy/Ship via Flow Builder 2.0
Same here. I can't ship a workflow that uses Postgres nodes. But was able to ship a workflow which uses one custom-made node (the whole workflow is super short, just REST API trigger, one custom-made node, and output).
As someone wrote a couple of days ago in the general channel, I love and hate Buildship at the same time. I already started yesterday to use another platform for my backend tasks and will leave on Buildship only those functions that I haven't figured out how to do somewhere else (because of imported libraries).
43 replies
BBuildShip
•Created by Christopher30 on 11/19/2024 in #❓・buildship-help
Sending data from Tally
Agree, I like that on Buildship we can build our own custom nodes, import libraries, etc. It also processes the data faster and as you mentioned, can do parallel actions. But, as with many new products, it comes with some downside.
Also, I am not sure about the new pricing model when we are charged 1 credit for each node and 1 credit per second if it takes longer than 3 seconds to complete the node. I think workflows with AI components will be more expensive to run. Also, more complicated workflows where many nodes are involved.
12 replies
BBuildShip
•Created by Christopher30 on 11/19/2024 in #❓・buildship-help
Sending data from Tally
Thanks, I did the same yesterday - receiving data from Tally on Make and then sending only the fields that I need to Buildship. Implemented it as a fast, short-term solution to get things off the ground.
12 replies
BBuildShip
•Created by jeff_sss on 11/20/2024 in #❓・buildship-help
Cannot Deploy/Ship via Flow Builder 2.0
No, it sounds like you are in a worse situation than me. I am just trying to build some new flows to launch a product.
I tried to deploy some generic test workflow by adding only a trigger and a node that scrapes data from a URL. That worked.
Then I tried to add the "Postgres Fetch Table Data" node but didn't change anything in the code and the deployment Failed. However, if I test the node, it works perfectly fine.
@Gaurav Chadha
43 replies
BBuildShip
•Created by jeff_sss on 11/20/2024 in #❓・buildship-help
Cannot Deploy/Ship via Flow Builder 2.0
I have the same issue. Built a new workflow using V2. Trying to deploy it, but it fails. However, when I run a test, all nodes work without any errors.
43 replies
BBuildShip
•Created by Chris Wright | Brandmember on 11/19/2024 in #💬・general
Chris Wright | Brandmember - Has the log in cha...
I think Buildship has always been only these two options, no signups with regular email option.
3 replies
BBuildShip
•Created by Brian on 11/19/2024 in #❓・buildship-help
Unused New Line characters
Yes, use markdown formatting for prompt text.
5 replies
BBuildShip
•Created by Christopher30 on 11/19/2024 in #❓・buildship-help
Sending data from Tally
Edit: The "fields" array holds 4 objects (not one).
Didn't find "Extract from Array" node.
"Concat Property Values" node is not a solution for this.
12 replies
BBuildShip
•Created by Powerhouse on 11/17/2024 in #💬・general
Powerhouse - Is there anyone that has successfu...
Just to be sure, you want to call one of the APIs from RapidAPI in your Buildship workflow, right? Or do you want to publish something on RapidAPI?
If it is the first one, you must have your x-rapidapi-host and x-rapidapi-key (saved as secret) as your variables, other variables would depend on your specific case.
4 replies
BBuildShip
•Created by Powerhouse on 11/17/2024 in #💬・general
Powerhouse - Is there anyone that has successfu...
Yes, I have. But I didn't use the API node, instead, I used the Empty Node and wrote the code.
4 replies
BBuildShip
•Created by dbrwk on 7/4/2024 in #❓・buildship-help
Object Validation node returns Unsupported type: timestamp error
You should add it to "firestore create doc;"
5 replies
BBuildShip
•Created by dbrwk on 7/4/2024 in #❓・buildship-help
Object Validation node returns Unsupported type: timestamp error
I am using timestamp when updating field values for Firestore documents.
In node logic code you could modify the first line to this: import { Firestore, Timestamp } from '@google-cloud/firestore';
then you should be able to get the right time format by using:
"created_at": Timestamp.now()
//In my case I have coded to update the timestamp value right in the node logic, instead of having it as an input value.
Note: I am not a coder myself, I used AI to help me create the code for my node, but it works for me 🙂
5 replies