Pipeline Error trying to Create a Record
I am not a fan of Pipelines. I miss Automations. I used to be able to build an Automation in like 30 min and it did what I wanted. I've been working two days to build this Pipeline, even using the AI to do the framework, and I get nothing but errors or issues like this one. The intent of this pipeline is, if a record is created/updated in one app, it will look to see if there is a matching record in another app. If there is a matching record in the other app based on a site # & uniquely created identifier, it will update any modified changes in the second app. If there is not a matching record, it will create one in the second app. After tweaking several different things, I finally got it to create the record. At first, it was saying it was finding a record that matched the criteria despite no record being present. But now, whenever it does the search for a "Matching Record" based on the criteria I asked it to look at (site & unique identifier), it continues to have a FALSE finding and just creates a duplicate instead of updating. And the Activity log seems to say that it couldn't find the record based on the search criteria but created duplicate records with the exact criteria it was asked to look for. (I now have 5 records with identical site #s and unique #'s. What am I missing to get it to have a TRUE finding of the record. Also, is there any way to change the "Query" to look at anything besides the Record ID??
QuickBase Pipeline Best Practices
After working with QuickBase Pipelines for years, one thing is clear: Every real-world use case is unique, from API limits and Jinja logic quirks to race conditions or silent failures. That’s why I believe we need more shared knowledge and real-time collaboration around building smarter Pipelines. What I’ve learned: Pipelines are incredibly powerful but not always intuitive. The best solutions often come from hands-on trial, error, and teamwork. Every failure teaches us something about logic, structure, or scalability What I’ve learned: Share lessons from the field Explore patterns that reduce manual tasks outside the system Let’s learn by doing — together. #QuickBase #Pipelines #Automation #LowCode #WorkflowAutomation #NoCodeDevelopment #QuickBaseCommunity #APIIntegration #ProblemSolving
Document Template Save PDF to field in Record API Pipeline
I have been wracking my head all day on this. I was reading Generate Documents from your records in your app where it says "However, you can also create API calls and use Pipelines, code pages, or custom integrations to generate documents. Each part of the formula represents an API parameter.". I was using Restful "Generate a Document" and was able to make a request: How do I get the output of making a request or basically the document template for this record as a file attachment in the record? I tried using: <qdbapi> <rid>1700</rid> <field fid="22" filename="Model_T.jpg"> Base64 encoded file content</field> Thank you so much!
Pipeline after import (heavy traffic/transient error)
I am trying to improve pipeline performance and need guidance on the best approach please. When approx 1000 records are created from csv import using ImportExport action in TABLE A, the pipeline should look for TABLE B ID based on a text field in TABLE A and relate. Attached sample pipeline. When records are imported, the pipeline runs, but noticed the traffic warning. Bulk upsert may not work as each pipeline trigger is on single record update.
HTTP Request - Body
Hey Y'all. I have a question on how the Body works in the HTTP Pipelines Channel. Before I begin I have everything working and set up correctly (Was able to do it in Postman and was able to do GET Requests in Pipelines) I cannot figure out how to insert my body in HTTP node. I have tried a lot of things to get this to work. I double checked the encoding but maybe there is another option I need to use? I think my problem lies in the to__json Jinja function (If i even need to use it) Any tips are appreciated!! This body I was able to use in Postman and it worked!
Looking for Date/Time Field 1 = Date/Time Field 2 pipeline jinja
I begin with one trigger step and in the next step I need to filter records to match date time fields in both tables. My workaround is the native "is on date" filter but it would be best if I could include the timestamp portions of the field. Is there a way to format jinja to accomplish this? I've tried several variations but here is an example of one. {% if a.pull_date == b.pull_date %} {{"TRUE"}} {% else %} {{"FALSE"}} {% endif %}
