Sending data from Tally
I want to send data from Tally form submissions to the Buildship workflow. However, in the data structure, I can't access each of the key-value pairs from my form's questions. Instead, I can only take "fields" in an array format (holding an object inside, an object has all key-value pairs).
What would be the best way to extract this object from an array? I want to be able to use each of the key-value pairs in different nodes.
8 Replies
AI Support Bot Information
<@750455891878215831> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
To extract an object from an array in a BuildShip workflow and use each key-value pair in different nodes, you can follow these steps:
1. Parse the Input: Use a node like the
Parse JSON node to convert the incoming JSON string into a usable JSON object within your workflow, if your input is in string format.
2. Access the Object: If you have an array containing an object with key-value pairs, you can use the Extract from Array node, which allows you to access the object at a specific index. This is useful when you have an array with a single object.
3. Access Individual Key-Value Pairs:
- Once you have the object, you can use the Extract Key-Value node or equivalent logic within a Script node to extract specific keys and their values.
- When configuring nodes later in the workflow, you can use the extracted values directly by referencing them.
4. Utilize the Key-Value Pairs in Nodes:
- You can now use these individual key-value pairs as inputs to other nodes in the workflow, thus making it possible to perform specific operations with each piece of data.
5. Testing:
- Run the workflow with sample data to ensure each key-value pair is being accessed correctly and is used as expected in subsequent nodes.
If you encounter specific technical constraints or require detailed assistance with particular nodes, you may need to explore the BuildShip documentation or the available nodes in the BuildShip Node Library for tailored solutions.
BuildShip AI Support
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.
not sure which plan you are one, try to use the AI to generate the node for you to dissect the objects (I assume that you can see the raw data from the "fields")
I have another short-term bypass solution for you which has worked out for me.
signup a Zapier or MAKE account, which you will get free credits per month.
send the Webhook to Zapier or MAKE from Tally Form, then, break the fields apart and POST them to BuildShip.
I am a heavy user of Jotform, this has worked out for me in the past (if Zapier does not parse the response, then use MAKE to POST to Zapier, and vice versa)
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.
Awesome, Chris. Although none of the apps are perfect, however, I have to admit, BuildShip is a lot more customisable than Zapier or MAKE, especially when it comes to "parallel" actions.
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.
yeah, totally, although I know some of the users said that the overall usage is cheaper than Zapier and MAKE. I am still observing the new pricing system.