Integration lifecycle management now supports pull, visual diff, merge, snapshot, and revert
Integration lifecycle management just got a lot easier. You can now pull and merge changes between integration clones, and you can see and reject visual diffs before changes are merged.
- Pull changes – safely make changes in a test/dev/sandbox integration, and then pull the changes into your production integration.
- View change diffs – compare all changes visually between two integrations before merging changes.
- Create snapshots – create a snapshot so that you can always revert to that working copy of your integration. Snapshots are also auto-generated when integrations are merged and reverted
- Revert – go back to a prior revision of your integration when changes introduce unexpected issues.
Preview import requests while developing your flow
You can now preview import requests while configuring flows with import steps that use HTTP-based connectors. This feature does not currently apply to database connectors, such as mySQL, Oracle DB, and Amazon Redshift. Import previews allow you to see the constructed request and a sample record that represents what integrator.io will send to the destination application. The import preview request will not be sent to the destination application unless you send a sample request.
Send sample requests
Click Send while previewing a sample import request to send the request you’ve constructed with a single sample record to the import API. The HTTP request tab displays the data sent, and the HTTP response tab shows the response returned by the destination application. The Parsed output tab displays the output from integrator.io that you can use as a reference when configuring response mappings, and to confirm a successful import.
A new GraphQL connector enables you to integrate with GraphQL endpoints to easily process GraphQL requests and responses.
Reduce script maintenance & make integrations portable with resource aliases
Instead of referencing specific IDs for connections, export, imports, and flows in scripts, you can now use aliases. Maintaining scripts is easier and less error-prone because you no longer have to manually change referenced IDs when new resources are available. Using aliases also prevents you from having to manually change IDs when you clone flows or integrations within the same account, and makes your integrations portable across accounts. You can also take advantage of aliases when defining transforms for flow steps, and in Form Builder when defining forms for custom settings.
Connectors are now available for Brex, Happy Returns, Microsoft Dynamics 365 Finance, and Microsoft Power Automate.
Parsed records include file size metadata
Each export that adds records to a flow’s data by parsing a file (such as XLSX or JSON) will also add a fileSize field to that record. Then, you will be able to check that value later, for example in an import when the server requires the size to be provided for an uploaded file.
New and enhanced templates
We’ve built new Marketplace (NA | EU) templates to help you jumpstart your integrations, most notably:
In addition, some of the more popular Quickstart integration templates have been updated with this release:
- (NA only) Concur Expense or Invoice – NetSuite: support multiple expense items
- (NA only) Concur Expense or Invoice – Acumatica: support multiple expense items
- Orderful – NetSuite: support multiple trading partners
- Jira Cloud platform – NetSuite: add NetSuite case attachments to Jira issue attachments
Increased file size limits for XLSX file processing
Flow Builder now allows increased file size limits for flow steps that download or upload an XLSX file:
- Export flow steps previously limited to 25 MB now allow a 100 MB file size
- Import flow steps previously limited to 5 MB now allow a 100 MB file size
Processing records that exceed the XLSX file size limitation requires you to convert the records to CSV format. For information on other formats, see Maximum file size limits.
Preview NetSuite import mappings
You can now see the structure of NetSuite source records and the expected output when you use lookup results, response, or import mappings. This feature helps you visualize mappings so you can verify the accuracy, identify errors, and debug issues before you run the flow. You can still use the NetSuite mapping assistant to review your subrecords.
Preview Salesforce import mappings
You can now see the structure of your Salesforce source records and the expected output when you use lookup results, response, or import mappings. This feature helps you visualize mappings so you can verify the accuracy, identify errors, and debug issues before you run the flow.
Error Management 2.0 enhancements
We are continuing to refine the user experience for Error Management 2.0 based on customer feedback:
- You can now click the Cancel run button at the top of the Run console to quickly cancel a run
- On the Errors list, Open errors and Resolved errors now appear on separate tabs (instead of a toggle button)
- You can now click on the Success link that appears for a flow step with no errors to see details (just as you can click on the number of errors to see details in cases where errors have occurred)
- When a connection is offline, this is now indicated in multiple locations
Override default webhook success response
When using the generic webhook listener, you can now customize or override the HTTP status code, media type, and HTTP response body for the HTTP response returned by integrator.io after a webhook request is successfully received from an application.
New Google BigQuery connection option: DB
A new Google BigQuery connector built to better support data warehouse integration is available under Databases when you create a connection. The existing HTTP-based BigQuery connector appears under the Connectors section and has been renamed Google BigQuery (REST API).
Amazon Seller Central connection updates
Amazon Seller Central connections no longer require authentication keys generated by the Amazon Seller Central Merchant account to be entered in the iClient field when you create a connection. Authentication is now handled with the Amazon Developer Keys managed by Celigo. To ensure your integrations will not be affected, open your Amazon Seller Central connection and delete any existing values in the iClient field.
HTTP connections now permit the underscore (_) character in URLs
You can now use underscore characters (_) in all URL settings throughout integrator.io, including in Base URI and Relative URI.
We’re continuing to improve prebuilt API connectors to align with the providers’ features and make the settings more intuitive:
- Amazon Redshift: renamed to include (REST API); moved from Databases list to Connectors
- BigCommerce: added API endpoints
- Concur Invoice: added API endpoints
- Coupa: OAuth 2.0 support added; Token now has [Deprecated] tag
- Freshdesk: added API endpoints
- Google Contacts: support for People v1
- JazzHR: added API endpoints
- Loop Returns: support for v2
- MercadoLibre: added API endpoints
- Microsoft Dynamics 365 Business Central: added API endpoints
- Miva: added API endpoints
- Recurly: updated for v3
- SAP Business One: added API endpoints
- SAP SuccessFactors: added API endpoints
- ServiceNow: new OAuth 2.0 type
- Shopify: removed ‘value-type’ (deprecated); connection form Version dropdown updated
- Square: added API endpoints
- Changes to the CSV file row delimiters on the export configuration screen were not correctly reflected in audit logs.
- FTP filenames that contained timestamps or UUID handlebars generated an error.
- NetSuite exports produced duplicate lines when NetSuite bundle components unexpectedly stopped and restarted.
- A script error in a preSavePage or postMap hook would cause the entire page of records to fail, instead of passing along the record where the error occurred, making troubleshooting difficult. Script errors now display the affected record.
- The ServiceNow connector’s Search parameters were not allowing auto-complete of handlebars expressions.
- The AS2 connector did not support Unicode characters in authentication criteria.
- The SalesForce – NetSuite (IO) Integration App would not allow opportunity splits in sales orders.
- NetSuite sublists didn’t include support for Cost Budget and Billing Budget.