What’s new
Apply branching logic in flow builder
Creating complex flows got a lot easier. You can now split exported data into different “branches” and then import each one into a different destination application, or send the records to a lookup for processing. You can also modify, delete, and merge branches as needed.
Set branching conditions using either rules or JavaScript. Two branching types are available:
- First matching branch – Records flow through only the first branch where the conditions are met
- All matching branches – Records flow through all branches where the conditions are met
You will see a change in Flow Builder with options for branching and enhancements for navigating horizontally and vertically. Existing flows will not be impacted by these changes.
Multifactor authentication
Protect your data from malicious intruders by enabling multifactor authentication (MFA). Three factors most strongly verify identity:
- Something you know – a password
- Something you have – a trusted mobile device
- Something you are – fingerprint, face, retina, or other biometric identifier
The more factors required for access, the more difficult it becomes for bad actors to plunder your data with a stolen profile. Use any MFA authenticator app that supports time-based one-time passwords (TOTPs) to verify identities with mobile devices to reduce security risks.
Audit tab now includes Access logs
New account-level audit logs let you track user activity in your integrator.io account, including who’s signed in or out – by IP address, when single sign-on (SSO) configurations are modified, resource change notifications, and changes to your on-premise agents. You can also filter by My API and Scripts, download only filtered data, and filter your data based on specific actions (created, updated, deleted, and so on).
New connectors
Prebuilt connectors are now available for Amazon Redshift (under the Databases section) and Bundle B2B. Updates to your account for the Narvar and Workday prebuilt connectors will follow this release.
The new Amazon Redshift connector – found under Databases when you create a connection – better supports data warehouse integration. The existing HTTP-based connector appears under the Connectors section and has been renamed Amazon Redshift (REST API).
What’s enhanced
Mapper 2.0 enhancements
Mapper 2.0 is more widely available and robust in this release:
- Mapper 2.0 is now available for file transfer-based imports such as FTP, AS2, and Google Drive
- Save time by filtering the list of source fields available in your flow
- Auto-populate the list of available fields from HTTP connector settings or via the sample file option in file transfer imports
HTTP enhancements
We’re continuing to improve the HTTP connector based on customer requests:
- You can now leverage the power of the new XML parser to convert XML responses to JSON for HTTP exports when you select the XML media type for success or error responses
- You can provide PFX files to add certificates in HTTP connections
- The size of http.auth.token.refreshToken_crypt is increased to 128 KB
Upload sample XML for file transfer imports
For file transfer (upload) imports, you can now provide a sample XML file.
Webhook listener signing algorithms
For a webhook listener that has the verification type set to HMAC, you can now select two additional SHA-2 algorithms: SHA-512 and SHA-384.
REST API connections redirect to HTTP
Creating a universal REST API connection will redirect you to the HTTP API connector form because it provides more stability, better functionality, and additional settings that aren’t available in the universal REST API connector. Existing REST API connections won’t be affected and won’t be switched to HTTP connections.
Updated connectors
We’re continuing to improve prebuilt API connectors to align with the providers’ features and make the settings more intuitive:
- Faire – updated to v2 APIs
- Freshdesk – additional API endpoints available
- Gorgias – switched from password to API key
- LogiSense – Store URL connects to the latest version
- Microsoft apps (various) – scopes fixed and aligned
- Shopify – new scopes; additional endpoints; v2 added to auth URL; access tokens sent at the header level
- Skubana – migrated from REST API to HTTP
- Slack – new scopes; additional endpoints; v2 added to auth URL; access tokens sent at the header level
- Square – removed deprecated endpoints
Automate backup of integrations
You can now automate backup of integrations and create snapshots via integrator.io API endpoints for Integration Lifecycle Management. You can also choose to create a snapshot only when changes are made in the integration or skip if no changes are made.
NetSuite mappings now support {timestamp} expression
You can now correctly resolve the {timestamp} helper anywhere in your flow where handlebars are allowed. Previously, it worked in all settings and the Dev playground, except for NetSuite import mappings.
Single sign-on (SSO) subscription-based
You can use the premium SSO feature for improved security and a streamlined user experience. If this feature is a part of your subscription plan, then you can create an SSO-enabled account and enforce secure access for users. Otherwise, you can upgrade your subscription plan to enable it.
What’s fixed
Customer-reported issues resolved
- A conflict in the field debugUntil was preventing a merge from source integration into the clone when debug mode was enabled for resources at both places pulled
-
The Loop Returns v1 connector was revised to use relative URIs \allowList and \blocklist instead of \whitelist and \blacklist
-
Certain downloaded Excel files could not be parsed
-
Error retry data is now stored for 30 days after each attempted retry (previously, the error data was stored for 30 days after the initial error)
-
Integration app homepages would generate a permissions error for account managers
-
Data loader flows to NetSuite were not converting date formats as expected
-
AS2 listeners did not support XML format
-
NetSuite import mapping and lookup criteria did not offer selection of internal or external IDs for transactions
-
Import mappings with exceptionally large numbers of mapped fields could cause the browser to time out
-
Cloned dynamic lookups to NetSuite and Salesforce failed to refresh metadata upon installation, removing the mappings for recently created fields
-
Imports to NetSuite did not support subrecord mapping for bin transfers
-
PGP encryption failed for files that contained special characters
-
Concurrency ID lock template for “Path to many” imports did not inherit the correct path, and instead referenced the parent root path
-
The Quickbase connector generated errors on preview
-
WooCommerce delta exports sometimes failed to retrieve all orders as expected
Tell us what you think: You’re invited to share your opinion on specific features and the overall release (estimated time: 60 seconds).
Support: Help Center updates
The following articles have been added to Celigo integrator.io documentation:
- Building GraphQL queries
- Set up an OAuth 2.0 HTTP connection to Amazon Vendor Central
- Set up a token-based HTTP connection to Amazon Vendor Central
- Set up a basic auth HTTP connection to Microsoft Dynamics 365 Business Central On-premise
- Mapper 2.0 (beta)
- Sign in using single sign-on (SSO)
- Supported Concur Expense and Concur Invoice APIs
- Set up a connection to Constant Contact
- Set up a connection to Google Ads
- Set up an OAuth 2.0 HTTP connection to Microsoft Dynamics 365 Business Central export and import data via custom APIs
- Supported Microsoft Power Automate APIs
- Configure EDIFACT files
- ServiceNow FAQ
- Marketo – Microsoft Dynamics 365 CRM templates
- Reauthorize your Microsoft Dynamics 365 Business Central connection
- Creating custom fields and installation packages for Salesforce templates
- Creating custom fields and installation packages for NetSuite templates
- Creating custom fields and webhooks for Jira templates
- JSONPath notation
- Concur Expense (Best Practice & Enhanced) – Microsoft Dynamics 365 Business Central
- Concur Invoice (Best Practice & Enhanced) – Microsoft Dynamics 365 Business Central
- Concur Expense – QuickBooks
- Audit logs
- How much capacity does my account have?
- Analyze integration and flow metrics
- Explore the integration dashboard
- Manage your Settings tab
- Monitor flows in an integration
- Filter the run history
- Review your integration connections
- Update your integration Admin tab
- View your authorized users
The following articles have been updated for Celigo integrator.io documentation:
- Concur export workaround
- Intro to Error Management and related articles in the Handling flow errors section: Revised to remove references to different versions of Error Management as all accounts have now been migrated to use the latest features.
- integrator.io API management section revisions include updates to definitions and new and updated API endpoints:
- Getting started with standard REST API
- Connection API endpoints
- Export API endpoints
- Import API endpoints
- Flow API endpoints
- File definitions API endpoints
- Integration API endpoints
- Audit API endpoints
- Jobs API endpoints
- Errors API endpoints
- State API endpoints
- iClient API endpoints
- Connector and License API endpoints
- Template API endpoints
Comments
Hi, just wondering will there be any downtime during this release. I'm asking this question because we have scheduled to run integration processes 24/7 and I would like to keep our business team in the loop in case if there is any downtime. Also, I'm assuming this is an automatic upgrade and no manual intervention is required from our side. Please confirm this as well.
Thank you,
Sai.
Great question, Saibaba Pokala. I will refer you to a very recent article, Find out about releases and version updates:
Thank you Stephen Brandt for clarifying my question and for providing reference for releases and version updates. This is very useful and informative.
Hi,
We have been experiencing issues with the Shopify to NetSuite Connector, orders not coming in and failing with the error:
Unable to create the order in NetSuite for the Shopify order #4934612746330 Failed to save record because Multi-location Inventory Error (MLI_LOCATION_REQUIRED): this transaction or its items must have locations.
Please advise if this is a systemic issue and if there is a quick fix. Also, do we need to update the Bundle on NetSuite?
Thanks!!
Hi, Guy Langley. I've been following your support request (#125811) and keeping an eye out for similar error reports, to see if a bug report would result. As far as I can tell, the issue is already resolved. Please reply if there's anything else we can do, or if you would like to share a caution for other customers.
Please sign in to leave a comment.