Sep 25, 2020 12:12 PM
My table has a column with a single image which I need to process via remove.bg (to remove background). I want the processed image to be loaded to a new column NEXT to the column with the original image. And I have many records in the table so I need the process to be automatic.
AirTable 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).
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.
I sent support request to Remove.BG but I don’t think this is an issue with Remove.BG. It’s a limitation with the AirTable ZAP in Zapier.
To get it working in Zapier, the Zap flow has 3 parts.
Part 1:
When this happens …
Part 2:
Do this …
2. Remove Image Background in remove.bg
This will process the image. Works fine and output is created.
Do this …
3. Create Record in Airtable
This will add the processed image to AirTable.
This step offers 3 Events
A) Create Record
Creates a new record with auto-populating fields.
B) Update Record
Update the values of specific cells in an Airtable record.
C) Find Record
Use simple field search or Airtable’s powerful formula syntax to find a matching Airtable record. Learn more at https://support.airtable.com/hc/en-us/articles/218151657.
The issue is - NEITHER of these work as I expect it to work.
Option A - create new record
Option A works fine but it creates the record in a new table. So I end up with a separate new table containing the processed images. To get the processed images back to my main table (containing original image) requires linking both tables using e.g. the Title field and doing lookup for the processed image field. This is way too complicated and messy and requires manual work to select the linked record.
Option B update SPECIFIC CELL
Option B would be perfect but the issue is Zapier only updates (= overwrites) specific FIXED CELL in table. 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. 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. So all new images will always overwrite the same cell.
Option C is to find a record.
Option C Event is to find a record. 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.
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.
Wondering if anybody got it working the way I describe. Remove.BG is a wonderful service to get pictures formatted for Amazon or other market places that required background free images.
UPDATE: I eddited the post to add clarity when referring to “CELL” instead saying "record"
Nov 29, 2020 05:40 PM
Found the issue with the small resolution. I didn’t realize it until I have generated 100’s of images. Didn’t realize they are uploaded to Google Drive but not to AirTable.
I posted here… you need to add one more step in the workflow.