2024 release notes
This page presents all release notes for Integrations during 2024, listed in reverse chronological order.
August 2024
New Features
Enhanced flow name visibility in filter dropdowns
Improved the flow name visibility in the filter dropdowns on the Executions, Containers, and Logs pages. With this release, when hovering over flow names in the filter dropdowns, the full flow name presents as a tool-tip if it is too long to display in the dropdown.
This provides quicker access to information, facilitating quicker understanding and navigation within the platform, and making it easier to identify and select specific flows for specific tasks.
Bulk flow Export feature
The new Exports dropdown menu offers users two options: Export Flow(s) and Export to a Recipe.
When Export Flow(s) is selected, users can choose one or multiple flows and export them simultaneously to any available contract and workspace as flow drafts.
This enables users to manage and export multiple flows. This, in turn, makes it possible to better optimize workflows and boost productivity.
More information about this feature is available in the core documentation.
Improved data visualization in JSONataView with label field display
Enhanced data representation in the JSONataView viewclass with introducing a label field display.
Users can now access and view the contents of the label field within JSONataView, as described in the component.json
file.
This allows for more precise data visualization and interpretation within the viewclass. It enables users to better understand and analyze the label field content within the JSONataView viewclass.
Unsubscribing from flow errors through API
A new API endpoint https://api.au.connect.squiz.cloud/docs/v2#/flows/delete_flows_subscription
allows users to unsubscribe either from flow errors across all their flows or flow errors within a specific workspace.
This allows integrators to more efficiently manage error notifications.
Default label display for router component branches
Users can now view the Default label associated with a branch of the router component directly on the flow queue page.
This update provides users quicker access to essential information, facilitating quicker understanding and more efficient management of the routing logic within the flow queue.
Updated status code 429 for exceeded Webhook requests limit
When the quota for Webhook requests is exceeded, the Webhook URL now responds with a 429 Too Many Requests
status code.
Symbols validation for credentials in the Webhook component
Users interacting with the credential fields of the Webhook component will now go through validation to identify unsupported characters.
If unsupported characters are detected, an error message — Disallowed symbol(s) — presents. This helps ensure data integrity and safeguards against unauthorized access.
|
Hide empty executions on the Execution page
A checkbox was added next to the filters that enables hiding executions without messages.
Checking this box removes empty executions from view.
This restricts the display to executions with messages, improving Execution page usability and, potentially, improving the efficiency of flow monitoring and analysis.
Handling unprocessed expiration errors from Kubernetes
Unprocessed expiration errors from Kubernetes are now handled.
A dedicated metric tracks and logs restarts associated with unprocessed expiration errors. The logs provide data for measuring and investigating system stability and performance.
Addressing UI freezing during large Sample loads
A new, more memory-efficient, library has been deployed, replacing the old library.
The new library reduces UI memory usage. In most circumstances, the result is a more responsive UI.
In testing, the new library reduced freezes to zero and provided a smooth workflow, even when working with large sample datasets
Fixed Bugs
-
HMAC sha256 authentication was not working with some external systems. Some external systems use different headers for passing the HMAC signature. A new field, Header Name, was added to the Webhook’s credentials with HMAC for custom header values. If not specified, a default value,
x-eio-signature
is used for this field. -
Predefined flow types — Ordinary or Real-time — are now applied on the Activate Recipe action.
-
A predefined CRON expression is now applied on the Activate Recipe action.
-
The error message
TypeError: Cannot read properties of undefined (reading 'filter')
presented on the Flows page, even when no flows are present. -
Snapshots were not being read properly within a single container. A new version of Sailor —
sailor-jvm:4.0.2
— has been released which addresses this.
Components
Microsoft Dynamics for Finance and Operations component 1.0.0
Initial component release
- Added
-
-
Make Raw Request Action.
-
Flow Linking component 1.1.0
- Added
-
-
Lookup by ID checkbox to Trigger another flow Action.
-
Retry errors checkbox to Trigger another flow Action.
-
- Fixed
-
-
Issue with Cannot read properties of undefined (reading 'data') in trigger another flow Action.
-
Socket Hang Up issue.
-
- Updated
-
-
Sailor version to 2.7.2.
-
AMQP component 1.4.3
- Updated
-
-
Consume trigger now locates the logs and messages in the last flow execution.
-
Sailor to v2.7.2.
-
amqplib
to v0.10.4.
-
Bynder Component 1.1.0
Initial component release.
- Added
-
-
Make Raw Request Action.
-
Lookup Object By ID Action.
-
NetSuite REST API Client Credentials component 1.0.0
Initial component release.
- Added
-
-
Make Raw Request Action.
-
Git-Protocol component 1.2.4
- Added
-
-
Option to provide either the Maester Object ID or the Maester Object URL as input in the Create Commit Action.
-
Rest API OAuth2 Client Credentials Component 1.2.0
- Added
-
-
Maximum response size in bytes configuration field to HTTP request Action.
-
Splitter component 1.5.0
- Revitalized
-
-
Re-assembled Message Action - now all messages are stored in memory within the component and saved to the external storage (Maester) only when needed.
-
- Added
-
-
New checkbox Emit result as array to Re-assembled Message Action.
-
- Updated
-
-
Sailor version to 2.7.2.
-
- Fixed
-
-
Vulnerabilities in dependencies.
-
May 2024
New Features
- Real-time webhook flow option
-
We now provide the option for integrators to turn their webhook flows into real-time mode. This change reduces latency for starting the flow if it is not already running.
For flows that run on a scheduled basis, there is no need to make any changes. Ordinary flows will continue to function as usual.
- New quota types for webhook calls
-
We have implemented new quota types to enhance control over webhook calls per minute:
These quotas enable fine-grained management of webhook usage, ensuring optimal performance and resource utilization. The default limit is 120 requests per minute.
- per_contract_request_webhooks_per_minute_limit
-
This controls calls to webhooks per minute at the contract level.
- per_workspace_request_webhooks_per_minute_limit
-
This controls calls to webhooks per minute at the workspace level.
Please contact support (support@squiz.net) if your contract needs to change the limit.
- Exceeding quota errors
-
Once the number of requests exceeds the limit (the default is 120 webhook requests per minute), further requests will be rejected with an error, and no messages will be queued. { "error": "Request quota exceeded: contract 5b5ed1cf272cf80011ae7b43 (false) | workspace 59d341e9037f7200184a408b (true)", "requestId": "9a315b2c476bd2c6f40a8d739d3f348e" }
- New Dashboard metric: Messages in Queues
-
The new Messages in Queues metric provides valuable insights into the status of unprocessed messages and offers a detailed list of flows along with their respective message queue counts.
You can monitor message queue performance, ensuring efficient message processing across your workflows.
The counter shows the total number of messages in the queues. Click the counter to see more details. - Run Now button in Flow Designer header
-
The Run Now button is now available in the header of active flows, allowing users to effortlessly initiate the run-now functionality directly from the flow designer interface.
- Improved email template
-
The transactional emails for deleting Workspace/Contract/Membership actions contain the user’s name who triggered the deletion process.
Added a new environment variable,
USER_NAME
, to the email templateworkspace-invite-new-user
.This variable dynamically populates the receiver’s full name (
firstName
andlastName
) in the invitation email.The email notifications can now be personalized with the recipient’s name, creating a more engaging and tailored experience for new users joining your workspace.
- Updated the Credentials section UI with checkboxes
-
Updated UI for the credentials section, implementing a cleaner and more user-friendly checkbox design.
- Added support for flow variables in recipes
-
The Recipe author can declare variables in the Recipe and use their values in the Flow templates.
The user can access these variables through $getFlowVariables().{variable_name}.
The usage example of storing these variables can be found in the
You can find examples of how to use these variables in the API documentation’s Recipes endpoint, under Parameters.
- HMAC SHA-256 authorization method
-
SHA-256 encryption algorithm is supported in Webhook credentials.
- Increased time of possible restoring flow before permanent removal to 48 hours
-
CronJob value responsible for the time of possible flow recovery before permanent deletion is increased to 48 hours.
- Beautify cUrl in the Implement section of the flow-designer
-
The appearance of the JSON in the Implement section has been optimized so that it is easier to read the flow’s structure.
- Enable Subscribe to errors by default for the flow creator
-
Subscribe to errors feature is automatically activated for the flow creator by default. Users can unsubscribe to errors through the Settings menu on the Flow card. Also, any user can subscribe to flows that are not theirs in the workspace.
Fixed Bugs
-
Random plus and fork icons are displayed on the flow-designer page after adding a step in the middle of the flow.
-
Cases with no new threads if the trigger hasn’t emitted the messages.
-
Snapshots don’t work for JAVA-based components.
-
Subscribe to errors check mark disappears after UI reload.
-
$getPassthrough()
function is unavailable in the UI when the previous step’s sample is an array. -
The Grant/Revoke support access button is not displayed on the Workspace page if configured on the tenant level, not per contract.
-
The monitor-contract-quota-usage job does not send an email if the quota is exceeded.
-
The quota usage page cannot load reports if you have many workspaces.
-
k8s-events-handler
reconnection issue.
Components
Deepl component 1.0.0
Initial component release
- Added
-
-
Make Raw Request Action
-
Translate Document Action
-
Translate Text Action
-
Monday component 1.0.0
Initial component release
- Added
-
-
Make Raw Request Action
-
Lookup Objects (plural) Action
-
Lookup Object By ID Action
-
Notion component 1.1.0
- Added
-
-
Archive Object Action
-
Lookup Object (at Most One) Action
-
Lookup Objects (plural) Action
-
ChatGPT component 1.1.0
- Added
-
-
A field that allows to specify an API call request timeout to the Send Request Action
-
The list of models in the Send Request Action is now dynamic
-
Shopify Admin v2 component 2.4.0
- Added
-
-
Emit an empty object if no entities found checkbox to Lookup Objects (plural) Action
-
Transformation (JSONata) component 1.0.13
- Updated
-
-
Sailor version to 2.7.2.
-
@core/component-commons-library to 3.2.0.
-
Node.js Code with credentials component 1.0.0
Initial component release
The component is derived from the code-component 1.2.11. |
A noteworthy enhancement in this version is the introduction of an authorization mechanism. This mechanism involves the use of credentials, which are available in four distinct types:
-
No Auth
-
Basic Auth
-
API Key
-
OAuth 2.0
August 2024
New Features
Enhanced flow name visibility in filter dropdowns
Improved the flow name visibility in the filter dropdowns on the Executions, Containers, and Logs pages. With this release, when hovering over flow names in the filter dropdowns, the full flow name presents as a tool-tip if it is too long to display in the dropdown.
This provides quicker access to information, facilitating quicker understanding and navigation within the platform, and making it easier to identify and select specific flows for specific tasks.
Bulk flow Export feature
The new Exports dropdown menu offers users two options: Export Flow(s) and Export to a Recipe.
When Export Flow(s) is selected, users can choose one or multiple flows and export them simultaneously to any available contract and workspace as flow drafts.
This enables users to manage and export multiple flows. This, in turn, makes it possible to better optimize workflows and boost productivity.
More information about this feature is available in the core documentation.
Improved data visualization in JSONataView with label field display
Enhanced data representation in the JSONataView viewclass with introducing a label field display.
Users can now access and view the contents of the label field within JSONataView, as described in the component.json
file.
This allows for more precise data visualization and interpretation within the viewclass. It enables users to better understand and analyze the label field content within the JSONataView viewclass.
Unsubscribing from flow errors through API
A new API endpoint https://api.au.connect.squiz.cloud/docs/v2#/flows/delete_flows_subscription
allows users to unsubscribe either from flow errors across all their flows or flow errors within a specific workspace.
This allows integrators to more efficiently manage error notifications.
Default label display for router component branches
Users can now view the Default label associated with a branch of the router component directly on the flow queue page.
This update provides users quicker access to essential information, facilitating quicker understanding and more efficient management of the routing logic within the flow queue.
Updated status code 429 for exceeded Webhook requests limit
When the quota for Webhook requests is exceeded, the Webhook URL now responds with a 429 Too Many Requests
status code.
Symbols validation for credentials in the Webhook component
Users interacting with the credential fields of the Webhook component will now go through validation to identify unsupported characters.
If unsupported characters are detected, an error message — Disallowed symbol(s) — presents. This helps ensure data integrity and safeguards against unauthorized access.
|
Hide empty executions on the Execution page
A checkbox was added next to the filters that enables hiding executions without messages.
Checking this box removes empty executions from view.
This restricts the display to executions with messages, improving Execution page usability and, potentially, improving the efficiency of flow monitoring and analysis.
Handling unprocessed expiration errors from Kubernetes
Unprocessed expiration errors from Kubernetes are now handled.
A dedicated metric tracks and logs restarts associated with unprocessed expiration errors. The logs provide data for measuring and investigating system stability and performance.
Addressing UI freezing during large Sample loads
A new, more memory-efficient, library has been deployed, replacing the old library.
The new library reduces UI memory usage. In most circumstances, the result is a more responsive UI.
In testing, the new library reduced freezes to zero and provided a smooth workflow, even when working with large sample datasets
Fixed Bugs
-
HMAC sha256 authentication was not working with some external systems. Some external systems use different headers for passing the HMAC signature. A new field, Header Name, was added to the Webhook’s credentials with HMAC for custom header values. If not specified, a default value,
x-eio-signature
is used for this field. -
Predefined flow types — Ordinary or Real-time — are now applied on the Activate Recipe action.
-
A predefined CRON expression is now applied on the Activate Recipe action.
-
The error message
TypeError: Cannot read properties of undefined (reading 'filter')
presented on the Flows page, even when no flows are present. -
Snapshots were not being read properly within a single container. A new version of Sailor —
sailor-jvm:4.0.2
— has been released which addresses this.
Components
Microsoft Dynamics for Finance and Operations component 1.0.0
Initial component release
- Added
-
-
Make Raw Request Action.
-
Flow Linking component 1.1.0
- Added
-
-
Lookup by ID checkbox to Trigger another flow Action.
-
Retry errors checkbox to Trigger another flow Action.
-
- Fixed
-
-
Issue with Cannot read properties of undefined (reading 'data') in trigger another flow Action.
-
Socket Hang Up issue.
-
- Updated
-
-
Sailor version to 2.7.2.
-
AMQP component 1.4.3
- Updated
-
-
Consume trigger now locates the logs and messages in the last flow execution.
-
Sailor to v2.7.2.
-
amqplib
to v0.10.4.
-
Bynder Component 1.1.0
Initial component release.
- Added
-
-
Make Raw Request Action.
-
Lookup Object By ID Action.
-
NetSuite REST API Client Credentials component 1.0.0
Initial component release.
- Added
-
-
Make Raw Request Action.
-
Git-Protocol component 1.2.4
- Added
-
-
Option to provide either the Maester Object ID or the Maester Object URL as input in the Create Commit Action.
-
Rest API OAuth2 Client Credentials Component 1.2.0
- Added
-
-
Maximum response size in bytes configuration field to HTTP request Action.
-
Splitter component 1.5.0
- Revitalized
-
-
Re-assembled Message Action - now all messages are stored in memory within the component and saved to the external storage (Maester) only when needed.
-
- Added
-
-
New checkbox Emit result as array to Re-assembled Message Action.
-
- Updated
-
-
Sailor version to 2.7.2.
-
- Fixed
-
-
Vulnerabilities in dependencies.
-
May 2024
New Features
- Real-time webhook flow option
-
We now provide the option for integrators to turn their webhook flows into real-time mode. This change reduces latency for starting the flow if it is not already running.
For flows that run on a scheduled basis, there is no need to make any changes. Ordinary flows will continue to function as usual.
- New quota types for webhook calls
-
We have implemented new quota types to enhance control over webhook calls per minute:
These quotas enable fine-grained management of webhook usage, ensuring optimal performance and resource utilization. The default limit is 120 requests per minute.
- per_contract_request_webhooks_per_minute_limit
-
This controls calls to webhooks per minute at the contract level.
- per_workspace_request_webhooks_per_minute_limit
-
This controls calls to webhooks per minute at the workspace level.
Please contact support (support@squiz.net) if your contract needs to change the limit.
- Exceeding quota errors
-
Once the number of requests exceeds the limit (the default is 120 webhook requests per minute), further requests will be rejected with an error, and no messages will be queued. { "error": "Request quota exceeded: contract 5b5ed1cf272cf80011ae7b43 (false) | workspace 59d341e9037f7200184a408b (true)", "requestId": "9a315b2c476bd2c6f40a8d739d3f348e" }
- New Dashboard metric: Messages in Queues
-
The new Messages in Queues metric provides valuable insights into the status of unprocessed messages and offers a detailed list of flows along with their respective message queue counts.
You can monitor message queue performance, ensuring efficient message processing across your workflows.
The counter shows the total number of messages in the queues. Click the counter to see more details. - Run Now button in Flow Designer header
-
The Run Now button is now available in the header of active flows, allowing users to effortlessly initiate the run-now functionality directly from the flow designer interface.
- Improved email template
-
The transactional emails for deleting Workspace/Contract/Membership actions contain the user’s name who triggered the deletion process.
Added a new environment variable,
USER_NAME
, to the email templateworkspace-invite-new-user
.This variable dynamically populates the receiver’s full name (
firstName
andlastName
) in the invitation email.The email notifications can now be personalized with the recipient’s name, creating a more engaging and tailored experience for new users joining your workspace.
- Updated the Credentials section UI with checkboxes
-
Updated UI for the credentials section, implementing a cleaner and more user-friendly checkbox design.
- Added support for flow variables in recipes
-
The Recipe author can declare variables in the Recipe and use their values in the Flow templates.
The user can access these variables through $getFlowVariables().{variable_name}.
The usage example of storing these variables can be found in the
You can find examples of how to use these variables in the API documentation’s Recipes endpoint, under Parameters.
- HMAC SHA-256 authorization method
-
SHA-256 encryption algorithm is supported in Webhook credentials.
- Increased time of possible restoring flow before permanent removal to 48 hours
-
CronJob value responsible for the time of possible flow recovery before permanent deletion is increased to 48 hours.
- Beautify cUrl in the Implement section of the flow-designer
-
The appearance of the JSON in the Implement section has been optimized so that it is easier to read the flow’s structure.
- Enable Subscribe to errors by default for the flow creator
-
Subscribe to errors feature is automatically activated for the flow creator by default. Users can unsubscribe to errors through the Settings menu on the Flow card. Also, any user can subscribe to flows that are not theirs in the workspace.
Fixed Bugs
-
Random plus and fork icons are displayed on the flow-designer page after adding a step in the middle of the flow.
-
Cases with no new threads if the trigger hasn’t emitted the messages.
-
Snapshots don’t work for JAVA-based components.
-
Subscribe to errors check mark disappears after UI reload.
-
$getPassthrough()
function is unavailable in the UI when the previous step’s sample is an array. -
The Grant/Revoke support access button is not displayed on the Workspace page if configured on the tenant level, not per contract.
-
The monitor-contract-quota-usage job does not send an email if the quota is exceeded.
-
The quota usage page cannot load reports if you have many workspaces.
-
k8s-events-handler
reconnection issue.
Components
Deepl component 1.0.0
Initial component release
- Added
-
-
Make Raw Request Action
-
Translate Document Action
-
Translate Text Action
-
Monday component 1.0.0
Initial component release
- Added
-
-
Make Raw Request Action
-
Lookup Objects (plural) Action
-
Lookup Object By ID Action
-
Notion component 1.1.0
- Added
-
-
Archive Object Action
-
Lookup Object (at Most One) Action
-
Lookup Objects (plural) Action
-
ChatGPT component 1.1.0
- Added
-
-
A field that allows to specify an API call request timeout to the Send Request Action
-
The list of models in the Send Request Action is now dynamic
-
Shopify Admin v2 component 2.4.0
- Added
-
-
Emit an empty object if no entities found checkbox to Lookup Objects (plural) Action
-
Transformation (JSONata) component 1.0.13
- Updated
-
-
Sailor version to 2.7.2.
-
@core/component-commons-library to 3.2.0.
-
Node.js Code with credentials component 1.0.0
Initial component release
The component is derived from the code-component 1.2.11. |
A noteworthy enhancement in this version is the introduction of an authorization mechanism. This mechanism involves the use of credentials, which are available in four distinct types:
-
No Auth
-
Basic Auth
-
API Key
-
OAuth 2.0
March 2024
New Features
- Handle large data samples on UI
-
To optimize the flow designer UI performance, the platform will generate JSON schema instead of JSON for large data samples (>256 Kb). The sample data will contain a JSON sample from the schema instead of the full body from the message output. The user will receive a warning notification about it.
- thread_id returned in Response Headers in case the HTTP Reply component fails
-
To improve error tracking and debugging, the
thread_id
value is now returned as thex-execution-id
in the response header when a flow Webhook-Reply encounters an error before the Reply step, facilitating easier identification and resolution of failed webhook interactions.
Fixed Bugs
-
Spacing issues and one typographical error on the profile page for white-label tenants.
-
An error where it was not possible to create a new Workspace for the users with the Member role in the Contract.
-
A browser Error 401 due to a connection.sid cookie.
-
UI for the Workspace page for the Safari browser.
-
The
attributes.declarations.variables[].help.link
on the Recipe activation page. -
Missing tooltips in objects for the input metadata.
Component updatess
Notion Component 1.0.0
Initial component release.
- Added
-
-
Make Raw Request Action.
-
Upsert Object Action.
-
Google PubSub Component 1.8.0
- Added
-
New Subscribe Trigger (the old trigger is set as deprecated).
- Fixed
-
Dependencies.
Telegram component 1.0.0
Initial component release.
- Added
-
-
Make Raw Request Action.
-
Webhook Trigger.
-
Send File Action.
-
Send Message Action.
-
Salesforce component 2.8.3
- Added
-
A
baseURL
parameter in the Raw Request Action’s configuration of the Axios library.The component interface has not changed. This is a technical enhancement. It will not affect any of the existing integrations. Instead, it gives more flexibility to call other REST endpoints than the standard /services/data. - Fixed
-
A bug where component did not use
replayId
after error in Subscribe to PubSub Trigger.
SFTP component 1.7.0
- Added
-
New option Emit file content (Base64) to the configuration of two actions:
-
Download Files.
-
Download Files by name.
This option makes file content to be emitted as a message.
-
January 2024
New features
- Filter flows by components on the Flows page
-
A new filter Component is added to the Flows page. Using this filter the system will filter and display the flows that contain selected components. The filter is multi-select.
The new filter option
component_id
is also added as part of theGET v2/flows
API endpoint to search by component name in the workspace. - CRON scheduling: Default cron expression - 10 minutes
-
Scheduling for CRON in the flows has been set to 10 minutes by default. To change it - open Settings on the flow designer page and set the required range.
- Label for the selected component
-
On the Flows page added a label for the selected component if the filter is applied.
- Suspend/resume flow feature
-
-
Suspend/resume flow with persistent queue
Suspend means that flows is not stopped and keep received messages and stored them in a queue. Once the status is changed from suspend to resume, all the messages will be resumed and passed through. If the flow is suspended, certain actions are enabled, such as changing the component version, mapping and credentials, but you will not be allowed to make any change in the flow graph UI.
-
Suspend flow button
-
Added Suspend flow to the menu of a flow card
-
Added Suspend flow button to the flow designer page
-
For the suspended flow, it is prohibited to change the flow graph. -
- Transformed UI for Workspace page from Ember to React
-
The React styles were applied to the Workspace page and all pages inside.
- Timestamp fields in the Contracts
-
Added created_at and updated_at attributes to the v2/contracts on GET, POST, and PATCH endpoints.
Fixed bugs
-
REMOVED Unnecessary warning messages during component executions
-
FIXED Webhook requests with malformed paths crush the platform services
-
FIXED Error in receiving sample Invalid username or secret provided.
-
FIXED
TypeError: Cannot read properties of undefined (reading localeCompare)
. -
FIXED Flow Designer UI crashes when metadata contains an array without properties.
-
FIXED
TypeError: Cannot convert undefined or null to object
. -
FIXED API pods restart due to Raven’s errors while connecting to Mandrill.
-
FIXED Bug with tenant admin permissions (PATCH contact’s customData).
-
FIXED API endpoint for adding an existing user to the specified contract has an incorrect body in Swagger.
-
FIXED Bug for cases where the flow was stuck in stopping/starting states after a manual restart.
-
FIXED Flows settings are not fully visible in the View list mode.
-
FIXED Stop Date on the container details page was equal to the current date-time.
-
FIXED Component logo fails to display after updating its visibility from Team to Tenant.
-
FIXED Error on Credentials Page in case the component hasn’t the title field (
TypeError: Cannot read properties of undefined
). -
FIXED Saving of data samples with specific structures.
-
CHANGED Incorrect validation of exitCode in k8s-event-handler.
Component updates
Facebook component 1.1.0
- Added
-
-
Upsert Object Action
-
Lookup Objects (plural) Action
-
Lookup Object (at most one) Action
-
Delete Object Action
-
X (Twitter) component 2.0.0
- Revitalized
-
-
Component and migrated on Twitter API v2
-
- Added
-
-
Make Raw Request Action
-
- Removed
-
-
Search Tweets Action
-
- Changed
-
-
Output metadata for Post Tweet Action
-
MongoDB component 1.6.0
- Added
-
-
Support for MongoDB latest versions (incl. 7.0)
-
- Updated
-
-
MongoDB Node.js driver to the latest version 6.2.0
Between MongoDB versions, certain things might have changed like the output format of data (metadata) emitted by some actions.
-
- No changes
-
-
For the old MongoDB versions (4.4 and older). MongoDB version can be chosen in the credentials.
-
- Removed
-
-
keepAlive
,useNewUrlParser
anduseUnifiedTopology
options in MongoDB for versions 5.0+ (still are available for older versions).
-
Mapper component 1.0.1
- Updated
-
-
Sailor version to 2.7.1
-
jsonata-moment to 1.1.5 that supports JSONata 1.8.6
-
Shopify Admin component 1.6.7
- Updated
-
-
The credentials verification process to not require any Shopify scope (previously:
read_products
scope). The platform now utilizes theget_shop
endpoint, which doesn’t necessitate any scope, as opposed to the previouslist products
endpoint.
-
Shopware 6 component 1.1.3
- Fixed
-
-
An issue when the component crashes due to the input metadata for the Upsert Object Action
-
An error in the Object Type selection for Lookup Objects (plural) Action
-
Salesforce component 2.8.1
- Added
-
-
new Subscribe to PubSub Trigger
-
Exponential backoff
-
- Fixed
-
-
Duplicate retries
-
Issue for real-time flows that sometimes have authentication errors
-
- Updated
-
-
Subscribe to platform events Trigger:
-
Fixed:
-
Duplicate retries if connections are lost
-
Incorrect behavior of AuthFailure
-
-
Microsoft PowerBI Component 1.0.0
- Added
-
-
Make Raw Request Action
-
Retrieve Reports Action
-
Pinterest Component 1.0.0
- Added
-
-
Make Raw Request Action
-
Make API Call Action
-