Skip to main content
loading...
3145 Topics

Common Problems with Airtable on Zapier

Instead of the values shown in a cell, we're getting a referenced cell's ID If instead of this: You get this: That means that these are linked records — in other words, they're being pulled from another table. We get IDs for those because the data being shown isn't actually in those cells. As a workaround, you can create a formula column and select the lookup column name as the formula. This pulls in the lookup values as text so they can come across to the Zap the way you would expect. I want to add multiple different values to my "Multiple Select" Airtable field but they're all merged If you're trying to add multiple options to fields like this: Separate the values with commas when mapping them in the Zap editor, either like this: Or by placing commas between fields you insert from a previous Trigger or Action, like this: My calendar views are not listed in the trigger's dropdown menu Zapier can only display the normal Grid view from Airtable when setting up the triggers. We do not currently support the Form, Calendar, Gallery, or Kanban fields. That said, when you create these views, you typically get to specify a new group or field to be created in the Main Grid view, and you can then use a Filter by Zapier step to check for that specific group or field you created for that view. The Zap will only continue if that group or field is coming from the trigger. My Airtable "New Record" or "New Record in View" trigger is only returning "created_at" and "id" fields, even though I have more data than that! Empty records in Airtable still count as trigger records to Zapier. So, if you have empty records at the bottom of your table, Zapier will pick those up in testing. Likewise, if you create new empty records (which Airtable may do automatically if you hit the 'enter' key while editing a record), those will trigger your Zap without any additional data. Then, if you update that empty record later to add data to it, it will not trigger your Zap. To fix this, make sure that you delete any empty records from your tables. A row was added to my Airtable view but it's not triggering my Zap Airtable only sends Zapier 200 rows from a view at a time. The row order is based on the created_date, so the newest created rows are at the top. If something was created months ago but now qualifies for the view, it may never be seen and thus not trigger the Zap. Here's an example: Let’s say you created 1 row on 2020-12-01 (we'll call this Row A). You then created 200 rows on 2020-12-02 (well call these Rows B). You then created 1 row on 2020-12-03 (we'll call this Row C). Then, on 2020-12-04, you updated all the Rows B to meet the criteria of the view. All of those would trigger the zap. Next, you updated Row A to meet the criteria of the view. This row wouldn't ever trigger the zap because it would be at the bottom of the list (since it was created before Rows B) and so it would be the 201st row. We'd never be notified about it. Finally you updated Row C to qualify for the view. This one would trigger because it would be the first row of the 200 that we'd see. One workaround here is that you can add an additional step to the end of your Zap to update something on the row, so that it's moved out of the view. That way the view will never grow above 200. Airtable is ignoring my date field If you are using Create Record or Update Record actions to update a record with a Date field, Airtable requires that the date/time be in "ISO" format. Any other format will be ignored. To update the record with the current time, you can use the Zap Meta Human Now timestamp to send the current time in UTC timezone, in ISO format, to Airtable. (Advanced) Searching for a table by name via Webhook fails If a webhook makes a request to https://api.airtable.com/v0/{appId}/{table name} it does not work with the User-Agent: Zapier header, which we automatically add. It returns a 404 (table not found) error. However, if you use the table ID, or if you remove the User-Agent: Zapier header, it will work. The preferred solution is probably to use the table ID. However, you can also make it work by adding a User-Agent header in the webhook fields, with any value that is not blank, and not Zapier. Summary: If you pass the table name, and if the User-Agent header is Zapier, it will return 404. If either of those two things is false, it works. Table ID & Zapier as User-Agent: 200. Table ID & not Zapier as User-Agent: 200. Table name & not Zapier as User-Agent: 200. Table name & Zapier as User-Agent: 404.

Common Problems with Squarespace on Zapier

Does the app need any special plan pricing? To use Zapier with Squarespace, you must be on the Website Business plan or higher. To learn more, visit their Premium features page.   My form doesn't appear in the Zap's dropdown menu Zapier can only receive data from Form and Newsletter blocks in Squarespace. Forms created as part of a Cover Page or a product order are not supported. As a workaround, you can configure other form types in Squarespace to use Google Drive or an email address as its storage. You can then trigger your Zap using the Google Sheets or Email Parser integrations. Note If your form is within a Form Block and doesn't appear in the dropdown, delete and recreate it within your Squarespace site. It should then appear when you refresh the Zap's dropdown menu.    I can't turn on my Zap, even though it tested successfully Squarespace only allows for one live Zap to be associated with a form, so if you have an existing Zap turned on that's connected to your form, you'll need to turn it off before turning on another.   I can't find the right form When you create a form in Squarespace, it will be named "New Form" by default. If you are seeing multiple forms with the same name in Zapier, change the names of your forms on your Squarespace site, then check again.   When I test a trigger, it doesn't show my data Squarespace only provides default data for trigger tests.   Squarespace is showing me the message "Status: Awaiting Connection" in the Storage tab of my form If you see this message, you need to complete the remaining steps of the connection process. You can find more details in this Squarespace help guide.  

Common problems with Evernote on Zapier

Can I trigger a Zap from a shared notebook?It's not currently possible to trigger a Zap from a shared notebook.Creating something from new notesCommonly, you'll want to create a contact, calendar event or something from a note, but such a pattern isn't very intuitive because Evernote doesn't have fields that map cleanly: they only have title and content and the other record might have first name, last name and email.One workaround is to place the name or email into the Note title, and some other field in the content. This way you can cleanly map the fields. At this time Zapier doesn't have the ability to intelligently "extract" values from a large body of text. You could also use something like named variables to manually mark data to be extracted.HTML or formatted notesBecause Evernote uses a unique type of HTML called ENML, we're not always able to format it exactly as you might expect. Instead, we do our best to strip down the content into plain text, and then place that plain text into the Note. This is a common issue with services like RSS, Gmail, IMAP or other email triggers which often have very unique HTML formatting. If you really want to add formatting to your note, double-check that it abides by ENML guidelines.Edits after creationWe will do our best to wait until you are done editing a note in Evernote before we trigger off of it. We do this by waiting until the last time updated stops changing, so you might see a slight delay on triggering as we need to see a note twice with no updates before we trigger it.Reminders are not triggeringRight now, we can only trigger on reminders if they are assigned due dates when they are created.My Evernote trigger is triggering slowlyIn order to ensure that we only trigger on new items that have complete information, your zap will make sure that a new item shows up with the same info in consecutive checks for new data. This can result in zaps triggering on new items more slowly. This is what we're referring to under Edits After Creation above.My link opens the Evernote web app but I want it to open the desktop appYou can make an in-app link (classic link) by typing the following and inserting the following fields:evernote:///view/[userId]/[shardId]/[noteGuid]/[noteGuid]/Please note that the note GUID is listed at the end of the link twice, sequentially.​Scanned business cards/contacts aren't workingUnfortunately, the business card scanner from Evernote doesn't work super well with Zapier. The issue is that all that information about the person's email/name etc is actually all in the body of a note, but with Evernote's markup language being used to make it appear pretty in the note. In order for you to be able to grab that data and move it to the action, we'd need discrete fields for each piece of information (name, email, etc), which Evernote doesn't provide.You could try a service like Full Contact instead, which would work well with Zapier.Evernote Error #2: The format of the request data was incorrect.This error can indicate a variety of problems in your Evernote Zap. The most common causes of this error are: The title of your note is too long: Evernote titles can only be 255 characters or less, so if you're pulling title data from your trigger, consider using a different field to populate your title. Trying to append to a note that doesn't exist: Make sure that the title of the note you're trying to append exactly matches the title of the note in your Evernote account:  Invalid attachments: When creating a note with an attachment, you must use either a file object or a direct download URL to a file –– other types of fields will not work:  Trying to write to a notebook that doesn't exist: If you've selected "use a custom value" from the Notebook Name, you'll need to have the Notebook's GUID, which will look something like this: Because this GUID is not likely to be provided by your trigger, using a custom value for your Notebook is not a common use case. Trying to add tags with the incorrect format: Tags must be added in a comma-delimited format. If you add them any other way, it will cause an error.

Common Problems with Asana

I'm not seeing my Project in the drop-down menuIf you're not seeing your Project listed, search for the project name in the field and click the "Check Asana & reload to bring in new choices" option:Projects are loaded from Asana 25 at a time so if you have a large number of projects in your account it might require more than one click in order for it to show up:I want to trigger on all tasks from all projects within a workspaceUnfortunately, there isn't a way to do this via Asana's API. One workaround is to use the "Tag Added to Task" Trigger, then add that Tag to each Task you want to trigger on in Asana.It's an extra step, but will save you from having to create a zap per project!Error message: Project: Unknown ObjectIf you get this error, the project you were using with Asana has likely been deleted. To fix this, go edit your Zap and select an existing project from your project dropdown for Asana.My new projects aren't triggering my zapUnfortunately, the New project trigger does not work for accounts with more than 1,000 projects. You'll need to clear out some old projects from your account to use this trigger.I can't find the tasks created via my "Create Task" action.While you can create tasks that don't have an assignee or project, those tasks are often difficult to find in Asana without searching for them. Only tasks that are assigned to you will appear in your My Tasks. Similarly, if a task does not belong to a project, it will not appear in any projects. We generally recommend that the Zap create the tasks with an assignee, or within a specific project. This way the task will be located within your My Tasks or the project when it is created.My Zaps are turned offIf zaps are turned off with this error message:try moving completed tasks into another project.This error can happen when you have a very large number of completed tasks in a project. Asana's API does not support filtering out completed tasks with pagination in the way Zapier expects. Our best recommendation is to move completed tasks to another project if possible. That should keep the number of incomplete tasks low enough for your zap to function properly. This error can happen in the following triggers: "New Task in Project", "New Subtask", "Completed Task in Project".