Ability for Zapier to work with reference fields.

When calling for a reference field, I would expect the following behaviours.

If an item doesn't exist, the CMS should create a new item in the referenced collection from the zap.

If an item does exist, the CMS should reference that item.

 

For multi-refs, the items should be comma separated then processed individually with the logic listed above.

  • Matthew P Munger
  • May 15 2018
API
  • Marcel McCarthy commented
    August 21, 2018 05:32

    YES!

  • Connor Finlayson commented
    September 12, 2018 04:30

    YES

  • Connor Finlayson commented
    September 12, 2018 04:30

    actually couldn't agree more. This functionality with AirTable would take my time savings to new heights!

  • Hamish Maclean commented
    October 29, 2018 07:38

    I nearly had a magical moment with a airtable > webflow zap where the client would not even have to login to webflow for a new event. But nope.

  • Tim Daff commented
    October 30, 2018 01:26

    Hi guys, I figured out a way to reference items via Zapier, so long as your use case is ok with having a predetermined list of collection options available to reference.

    For example in my use case / scenario.

    I have a "Product Code" collection, add a `Webflow UUID` plain text field, create a bunch of collection items, then use chrome dev tools to get the UUID for each one and save it to that item.

    I then have a Google Form our staff use to upload items to various collections.  The UUID's are "hard coded" into a Dropdown list on the google form, then populate to a sheet.  Zapier then picks up submissions, grabs the UUID and content, then populates the UUID in Product Code reference field.

    I find it very handy as you can have different collections referencing the Product Code and relate them in Collection Lists etc easily in webflow, and being zapier powered you don't have to use up any of your Content Editor spots for staff to add structured conent to the site.

    If anyone is interested in the method let me know and I'll write something up.

  • Hamish Maclean commented
    19 Feb 07:53

    That's a cool solution Tim Daff. Will try it out 

  • Marco Volpato commented
    20 Mar 14:57

    Hi Tim, any chance you could explain how this works/how you achieved it?

    I have a collection called Categories, and one called Posts.

    The Posts have a reference field where you can select a Category.

    I've set up a Zap that adds a new Live Item to Posts on my webflow site whenever I add a new row in my Google Sheet.

    So far, it works if I leave the Category reference field blank, but when I try to assign a Category by using the Category UUID (e.g. 5c47472e18f01b1ba434819d) it comes up with an error.

    I guess I have two questions:

    1. How do you find the UUID? I think I found out how (example above) but am not totally sure it's correct.
    2. Am I going about this the wrong way?

     Any clues would help!

    Cheers, Marco

  • Gene commented
    02 Jun 08:56

    This has been missing since 2017, any chance it will ever be implemented? Need this for a functional Zapier setup. 

  • Jesse Avshalomov commented
    12 Jul 19:35

    I found a workaround for this!

    (Part A): IDs -- To find the UUIDs for items that you want to reference, you can use a simple API call using the free tool Restlet. (Images attached of Restlet setup)

    1. Get your API key at the bottom of the Integrations Tab of your project settings.
    2. Use the List Sites API call to find your site IDs
    3. Use the Get Collections API call to get your list of collection w/ IDs
    4. Use the ID of the collection you want and the Get All Items in Collection API Call to get a list back of all your items, including their IDs!
    • Full API Calls listed at the bottom

    You can now use these in the references in Zapier!

    (Part B): Zapier -- As discussed earlier in this thread, the Webflow Zap for Create Item can't handle it when you enter an Item ID in a reference field. It chokes on it, end of zap. BUT, for whatever reason, entering an Item ID in a reference field in an Update Item Zap works just fine! (go figure, right?) 

    So you're going to break creation into two steps:

    1. Create the new item, with reference fields left blank
    2. In the next step, Update that newly created item, and enter in the IDs in the reference fields, and it works just fine. Viola! There are, however, a few quirks:

    - Use the Item ID from step 1 to find the Item for updating in step 2
    - All of your items Required Fields are STILL REQUIRED when Updating, which is a little silly. But just take the data from your Create Item Step and feed it back in for the Update Item Step and there should be no problem.
    - If any of your reference fields are Required fields, you'll need to go set them as Not Required in order for Step 1 to work (since you're leaving them blank). But it's a small price to pay for automation. 

    Good luck!

    ======== API Calls ===========

    Find Sites

    Find Collections

    Find Items

    • GET https://api.webflow.com/collections/COLLECTIONIDHERE/items 
    • Headers
      • Authorization : API KEY HERE
      • accept-version : 1.0.0