The State Changers meeting deliberated on working with APIs, manipulating form responses using Typeform, and implementing solutions using Xano. The key points of the meeting include:
1. Examination of API calls, where a test was performed resulting in a 500 internal error. This led to an investigation of request inputs and responses. 2. Dissecting the logic of a complex, branched form on Typeform and understanding the keys and ids associated with the fields was a significant part of the conversation. It was found that question ids are not fixed, which introduced an element of complexity. 3. The meeting further elaborated on how to link the responses from Typeform to Xano. The participants discussed using the 'find first element' function in Xano to retrieve specific responses based on the 'ref' id of the questions in Typeform. 4. During the meeting, the team also found that Typeform Designer URLs contained id references (ref), which could be used to identify specific questions in the form. 5. A detailed explanation of how to model data in Xano basing on the ref ids from Typeform was provided. This led to the conclusion that each question needed its own array in Xano for data organization. 6. Possibility "null" returns for the find first element function were also mentioned as a potential issue to handle. The participants did not explicitly mention any other tools or systems like WeWeb, FlutterFlow, Zapier, Make, Integromat, Outseta, Retool, Bubble, Adalo, AppGyver, AppSheet, Comnoco, Fastgen, Firebase, Google, OAuth, Stripe, Twilio, Airtable, DraftBit, Javascript, Typescript, React, Vue.js, JSX, HTML, CSS, lambda, serverless, State Change, ScriptTag, OpenAI, or AI21.
(Source: Office Hours 10/17 )
