![]() But if you have a need to send 50,000 emails in a month, it would only cost $20. I also really like using the Sendgrid extension (though this does incur additional monthly costs). ![]() You can also define a variety of ways for it to trigger including any changes to the record (checkbox, single select field using some sort of command like "Send email", etc. Other functional ways to schedule and send emails also include exactly what you've done with Zapier. You can even make the last action in an automation to update the record as "sent" as each email is sent. Turn on the automation after testing, and sit back and relax. After setting up the trigger, you can define the action (Send a Gmail) using the Integrations. You can set a variety of triggers (at a scheduled time, with your date/time modified field, or based on several filterable conditions). The most straightforward way that Airtable currently makes for that process is the use the Automation tab. There are quite a few different ways to send out emails from Airtable, as well as trigger them. Is this the way to do this sort of thing? It feels a bit clunky.Īnd, if you've had experience doing something like this yourself, was it smart for me to trigger the zaps in smaller batches? Or would Zapier have handled processing ~120 records in one run? After each batch went out, I marked those records as "sent" by hand (easy in Airtable, for this number of records), queued up the next batch, and waited for them to get sent. I didn't ask Zapier to do anything other than connect (record by record) to my client's Gmail account and send each message. ![]() We had to do a follow-up email, and I used the same process, just with a different body content for the message. I was a little worried about how well Zapier would perform, so I triggered smaller batches of records, about 30 at a time. ![]() The zap then connected to my client's Google Workspace/Gmail account to send the emails out. I defined a date-time modified field in Airtable that I used to trigger the zap in Zapier. The email contains a link to an Airtable form that I want them to fill out. I have a list of people (about 120) that I needed to send and email to. This week I used it for something important, and I'm wondering if the approach I took is the best way to solve the problem. Then we map the ID field from our Find/Create step.I've used Zapier on and off for the last couple of years for small purposes. How do we make it dynamic, so we update the person from our search step? You can’t choose a person from the dropdown menu, otherwise you’ll always be updating that same person every time the Zap runs. This is the part that trips up a lot of people. mine says FALSE because I created the person while testing the Zapįor the condition choose (Boolean) Is true: Instead, you can choose to only continue if the Zap Data Was Found field is TRUE. You could choose to always update the person, even if you just created them in the previous step, but all these extra tasks can add up if your Zap runs a lot. I then use the same mapped fields in order to create a person (if none is found).įilter (Technically optional)- Only continue if found I check the box for “Create Pipedrive Person if it doesn’t exist yet?” in order to make sure that if nothing is found, that I create a new person. I map the first and last name from my trigger step. I’m going to search by Name in Pipedrive, looking for an exact match. But, if you haven’t checked out our Chrome extension yet, now’s your chance!Īction - Pipedrive (Find or Create Person) This part isn’t necessarily important to you, aside from knowing that it’s how I’ll be adding data to the fields I then use in my action steps. I’ll then use Pipedrive for my action app since I used them as an example above. In this example I’m going to use the Zapier Chrome extension to trigger my Zap, since it’s an easy way to add data to a few fields and then trigger a Zap. In that case, you can either use two Zaps, with a filter in each (one for when something is found, and one for when it isn’t) or use our Paths function (again, one path for when you’ve found something and one for when you haven’t).ĪLSO IMPORTANT: You will also need your app to have an Update (insert your record type here) action, since otherwise you won’t be able to do anything once you find your record. Some apps have a Find action that doesn’t allow you to create an item if nothing is found. IMPORTANT: In order to do this most efficiently, you’re going to need an action in your app that allows you to find an item and create one if it’s not found.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |