Changelog

SDK developers can now:

1. Build multiple authentication flows—including OAuth2—into a single connector
2. Automatically enable PKCE (Proof Key for Code Exchange) for any OAuth2 authorization code grant 
3. Directly retrieve webhook URLs from recipe editor
4. Build hybrid (webhook and polling) triggers to poll for new records
5. Build refresh logic into your webhook triggers so there’s no need to refresh your webhook subscription
6. Create JSON web tokens (JWT) for a larger set of APIs with these new algorithms

Users can now create recipes that listen to deleted item events in Quickbooks. This enables accurate syncing of data between QBO and downstream systems like Shopify.

• Interested Customers: Verizon

• Sample recipes:

  • Sync items from QBO to Shopify Products

  • Syncs deleted items from QBO to Shopify Products

• On-prem files: Invalid character error for Windows file path format fixed
  

See OPA Release Notes in docs.

Users can now stream customer milestones from various systems like databases (for product usage), Docusign (for contract signing) or SkillJar (course completion) into Gong to gain a full 360 view into the events that contribute toward a successful sale or upsell.  To learn more, read docs and check the sample recipe Sync Docusign Contract event to Gong Deal.

Multitenant authentication support

• Users now have the ability to choose the “connection account type” and can sign in with a common, organization, or tenant-specific connection account type. Common supports personal, enterprise, and multi-tenant accounts, which are not tenant-specific. The organization supports multi-tenant enterprise accounts.

With the Recipe Diff feature, users can visually compare two versions of a recipe side by side—before choosing which to export.

This is handy for users who manage their team’s recipe development lifecycle.

To see how it works, check out Recipe Diff's documentation.

Automation HQ gives IT admins a central console to set up:

• Dedicated workspaces for business units (marketing, sales, finance, and HR etc.)
• User access and admin roles across workspaces
• Connections to your organization’s apps
• Usage policies and allocate resources like recipes and tasks

See more about Automation HQ in this blog post.

Self Service Flow Steps is a new Marketo feature. With it, users can build reusable custom steps that call out to other apps with customer data. 

While it can involve a lot of custom code to set up, Workato users can now create these flow steps the easier way: with a recipe.

Save weeks of development work when you use OpenAPI Specifications (OAS) to build your own custom Workato connectors.

Users have the option of creating a connector from an OAS document, or a sample code.

See more in the OAS generation documentation.

Embedded partners can now create custom apps (on supported connectors) and connect them to Workato. 

This gives partners control over the app’s branding, permission scopes, and OAuth profile. 

See the list of supported connectors and other details.