4/6/2024 0 Comments Google drive airtable zapier![]() ![]() Remove.BG is a wonderful service to get pictures formatted for Amazon or other market places that required background free images. Wondering if anybody got it working the way I describe. I am going to try Integrator to see how it is able to handle the Remove.BV and AirTable integration because I don’t see how this can work with Zapier the way I need it. I tried to experiment with this in hope it can solve the issue but I don’t see how it can resolve it, because if I use this event, I still have to add either Option A or Option B as s following step to get the data updated in AirTable. Update Google Drive files when Airtable records are new or updated. Create Swiss QR invoices and add them to Google Drive with new or updated Airtable records. So all new images will always overwrite the same cell. Upload Google Drive files for new records in Airtable. With this Event Zapier is fixated on a specific CELL in the table, so if I have 50 lines in the table, then all processed images are updated in the same field and every time a new image is processed in Remove.BG, it will OVERWRITE the previous processed image. That means, this Zap Event doesn’t upload the processed image into the same line record (same record ID) from where the original picture came. Option B would be perfect but the issue is Zapier only updates (= overwrites) specific FIXED CELL in table. This is way too complicated and messy and requires manual work to select the linked record. the Title field and doing lookup for the processed image field. To get the processed images back to my main table (containing original image) requires linking both tables using e.g. So I end up with a separate new table containing the processed images. Option A works fine but it creates the record in a new table. The issue is - NEITHER of these work as I expect it to work. Use simple field search or Airtable’s powerful formula syntax to find a matching Airtable record. Update the values of specific cells in an Airtable record. This will add the processed image to AirTable.Ĭreates a new record with auto-populating fields. Of course the new record will have the image I want to process. This is a trigger and it will start when a new record is added in my table. To get it working in Zapier, the Zap flow has 3 parts. It’s a limitation with the AirTable ZAP in Zapier. With Zapier, you can do more than just connect your apps - you can automate entire processes from beginning to end Check out the following list of triggers and actions you can use with Coda, Google Drive, and Airtable. ![]() I sent support request to Remove.BG but I don’t think this is an issue with Remove.BG. Do even more with Coda + Google Drive + Airtable. We are using Airtable as a database, so I have created a zap to create a new record in Airtable from the record in Google Sheets. Zapier flow works but the issue is, the flow doesn’t allow me to add the processed image in a new column next to the original image. And I have many records in the table so I need the process to be automatic.ĪirTable automation doesn’t seem to offer way to deal with REMOVE.BG so I am trying to setup Zapier (haven’t tried Integromat yet, but that’s another option). I want the processed image to be loaded to a new column NEXT to the column with the original image. Last I heard, the Airtable team was looking deeper into this issue.My table has a column with a single image which I need to process via remove.bg (to remove background). As you note, manually uploading seems to work fine which tends to rule out Google and the document itself or its permissions as the (at Airtable) has been very responsive to this issue and also agrees that it could be some sort of unknown issue lurking in attachment processing. ![]() To overcome this problem we believe we’re going to have to create a latent process that constantly looks for failed uploads and attempts to retry. This leaves me with great suspicion that the likely cause is Airtable. I crafted a number of metrics and even some additional processes to log failures and without question, I was able to rule out issues with Google Drive or latent permissions handling. The app in question was bullet-proof for three months and then this issue arose. I have spent the past 12 days fully documenting and testing uploads from Google Drive that started failing 1 and continue to fail roughly 30% of the time. I can confirm this is not a Google issue. Has anyone else experienced problems since then? Or is it a google issue perhaps? I am slightly suspicious that this started happening after Airtable did a update to reduce load times. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |