Versions Changelist#

Below is a changelog of the major releases of the Zapier Developer Platform. Each release has a summary of the new features added and any breaking changes that were made.

Version 2 (2015-07-31)#

This is a backward incompatible update to the Developer Platform. It adds several new features and fixes some of the limitations of the first version.

  • Apps can now have Searches. A Search is used to find individual records by a field (say finding a contact by name).
    • Searches can be linked with Actions to create a Search or Create flow, giving the user a way to search for an item, and if it doesn't exist, create it.
    • Searches can be used to power action fields, similar to Dynamic Dropdowns. Users input data to the field which is used to search for items, and a given data element returned from the search result (such as id) is used in place of their input.
  • Fields can now have the “List” property defined through the UI. Before this was only possible to set via Scripting.
  • Action fields have a “Parent Key” option that enables line item support.
  • Fields now have a "Placeholder" option that operates solely as an HTML5 style placeholder - it is only for helping the user understand what will happen if they enter nothing in the given field.
  • Breaking Change Scripting can no longer access trigger_data from bundle in pre_write and post_write.
  • Breaking Change Scripting can no longer access trigger and action from bundle.zap.
  • Breaking Change Scripting code now runs under JS strict mode ('use strict';), so developer should verify their code still executes correctly (the built in code editor runs jshint - so check there!)
  • Breaking Change Data mapped into Action Fields is always coerced according to the field's type
  • Breaking Change Data entering actions is no longer flattened into a string. This means lists and dictionaries will pass through to actions intact rather than being converted to CSV and 'key|value' respectively. If there is existing Scripting code that does any sort of parsing on those values, it will need to be updated to handle the new structure (likely this means deleting code that was expanding the strings back into arrays and dictionaries).
  • Breaking Change We now automatically include a state parameter on the Authorization URL for apps that use OAuth2.
  • Bug Fix Trigger fields passed into custom fields, REST hook and catch hook methods are always coerced according to the field's type

Version 1 (2012-08-01)#

The initial launch of the platform.

↑ Was this documentation useful? Yes No