In your case, you should be able to get the person’s name as one field and the record ID from your notes field. Then on my second Zap when the task is completed, I read the task name (person’s name and record ID) and use a couple of Zapier text formatter actions to get the record ID. (with a pipe separator) and in Todoist it looks like this: So, in my prototype, when I create the task in Todoist, I’m mapping the person’s name and the AT record ID to the task name - something like this: However, the principle should be the same, you just set it up on different fields. Hi - I managed to get this to work, albeit in a slightly different way to you as I don’t have a paid Todoist account and so don’t have access to task “notes”. I’m struggling to figure out how I can create a zap that finds the correct record so it can update the appropriate field I’ve tried passing the recordID to Todoist via the first zap (it’s currently stored in the Notes field in Todoist), but can’t figure out how to use that to query Airtable for the second zap.Īpologies if this isn’t clear - I’m new to both Airtable and Zapier and am trying to dive in. When the task is completed in Todoist, I want Zapier to update the ‘last contacted’ field for the correct record in Airtable to today’s date. If it is, the record is marked ‘Overdue’ there’s a view of all people in the base that filters to show only those records marked ‘overdue’.Įvery time a new record hits the ‘overdue’ view, Zapier creates a new task in Todoist to contact that person, along with their contact info. A formula calculates whether today is >= last contacted date + frequency days (+90, +180, +365). Here’s the general idea:Īirtable base: each record has a contact frequency (quarterly, semi-annually, annually, or none) and a ‘last contacted’ date. Can only be presented once in an issue.Hi - I’ve successfully created a Zap tied to a CRM base in Airtable. Select List (multiple choices/single choice)Īdvanced. You can find more information about the difference between "Standard" and "Advanced" fields in Jira's documentation. The names and types correspond to the custom fields in page /ViewCustomFields in Jira server. This list only consists of custom fields, not the system fields that are covered above. Airtable Sync overview - More information on limitations, dependencies, and more.Airtable Sync basic setup - Read this first if you've never set up a sync in Airtable before.This includes setting up the proper permissions in both Jira and Airtable's Admin Panel. Enterprise admins - Depending upon the account access you have at your organization, you may need to contact someone else to help with connecting Airtable and Jira together.Owners/ Creators - You'll need creator permissions to set up a Jira Server/Data Center sync in an Airtable base. These steps only need to be done once but are required. If you are setting up your organization’s first Jira Server sync, then please make sure that your organization's IT/Airtable/Jira admin(s) have reviewed our server and firewall requirements and taken the necessary steps before you connect your Jira Server account with Airtable.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |