So is there a way to change this so that “update” triggers are only sent every 5 minutes? That way we can complete all the changes to all the fields and then Zapier will get the whole lot in one go? I estimated that one Zap to update a Google sheet when an opportunity is updated could burn through our entire Zapier task allocation in just a few days from pretty light usage because Copper is triggering zap tasks for absolutely everything. That doesn’t sound like an issue until you get to Zapier and realise that every single one of these tiny changes is triggering a Zapier hook and burning through another bunch of tasks. I believe this is true for all content types. This means editing even 2-3 fields can trigger half a dozen “update” events, and going through updating a whole record could mean 10-20 separate “updates” all within a few seconds of each other. When editing an opportunity record, each time a field is edited this counts as an “update”. I suspect this applies to all the “Updated” zap hooks too. Remove.BG is a wonderful service to get pictures formatted for Amazon or other market places that required background free images.I have found a big issue with the “Updated Opportunity in Copper” Zapier link, and the problem seems to be on Copper’s side rather than Zapier’s. 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. So all new images will always overwrite the same cell. 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. I sent support request to Remove.BG but I don’t think this is an issue with Remove.BG. 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. My table has a column with a single image which I need to process via remove.bg (to remove background).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |