Controlling Data Storage for Specific Flows in Integration Logs

When businesses connect different systems and automate processes, information moves between applications every day. From customer details and financial records to internal business data, automated workflows help keep everything connected and running smoothly.

But not every piece of information needs to be stored after it has been processed.

Sometimes, data only needs to move from one system to another, without being saved in integration logs. Having control over what information is retained can help businesses better manage sensitive data, reduce unnecessary storage, and maintain cleaner records.

Choosing whether to store data from individual workflows provides greater flexibility in how information is handled.

Why Data Storage Control Matters

Integration logs are useful for tracking activity, reviewing workflow executions, and understanding how information moves between connected systems.

For example, when a workflow transfers customer information from a form to a CRM, integration logs can help teams review what happened during the process.

However, some workflows handle information that businesses may prefer not to retain in their logs.

This could include personal information, financial details, confidential business records, or other sensitive data.

Even when the information needs to be processed and transferred, storing an additional copy in an integration log may not be necessary.

Having the ability to control data storage at the individual workflow level helps businesses make more informed decisions about what information they retain.

Process Data Without Storing It in Integration Logs

A workflow doesn’t necessarily need to store the information it processes to complete its job.

For example, imagine a business using an automated workflow to transfer customer information from an online form to Salesforce.

The workflow receives the information, processes it, and sends it to the appropriate Salesforce record.

Once the transfer is complete, the business might not need that same information saved in its integration logs.

By disabling log storage for that specific workflow, the information can continue moving between systems without being retained in the integration logs.

The workflow still performs its intended actions. The difference is what happens to the processed information afterward.

Choosing Which Flows Store Data

Different workflows serve different purposes, and they don’t all need the same data retention settings.

A workflow that updates product information might benefit from detailed integration logs, while another that processes sensitive customer information may require a different approach.

Rather than applying the same storage rules to every workflow, businesses can choose which individual Flows should store their processed data.

With a Do Not Store Logs option available under Flow Settings, users can prevent information processed by a specific Flow from being saved or displayed in integration logs.

This provides flexibility without changing how the Flow executes or transfers information between connected systems.

Better Control When Handling Sensitive Information

Many business processes involve information that requires careful handling.

For example, an employee onboarding process might collect personal details and send them to an HR system. A financial workflow might transfer payment-related information between business applications.

In both cases, the information needs to reach its destination, but keeping an additional copy in integration logs may be unnecessary.

Controlling whether this information is stored can help businesses follow their internal data handling policies and reduce unnecessary retention of sensitive information.

It’s important to remember that disabling integration log storage doesn’t prevent the destination system from saving the information it receives. It simply controls whether the Flow’s processed data is retained in its integration logs.

This distinction allows businesses to continue using automated workflows while making more deliberate choices about data retention.

Reducing Unnecessary Data Retention

As businesses automate more processes, the amount of information moving between systems can grow significantly.

Some workflows run occasionally, while others may execute hundreds or thousands of times throughout the day.

When every execution stores processed information, integration logs can accumulate data that may no longer be needed.

Choosing not to retain data from selected workflows can help businesses:

• Reduce unnecessary information stored in integration logs
• Limit the retention of sensitive or confidential data
• Apply different logging preferences to different workflows
• Maintain greater control over how processed information is handled
• Keep automated processes running without storing every transferred value

The goal isn’t to eliminate integration logs entirely, but to make data retention a choice based on the needs of each workflow.

Finding the Right Balance Between Visibility and Privacy

Integration logs can be valuable when troubleshooting problems, reviewing activity, or understanding how automated processes behave.

At the same time, retaining every piece of processed information isn’t always the best approach.

For workflows that require detailed troubleshooting, keeping integration logs may be useful. For workflows that handle sensitive information, limiting what gets stored may be more appropriate.

The important thing is having the flexibility to choose.

By managing log storage individually for each Flow, businesses can balance operational visibility with their data retention preferences.

More Control Over Your Data

Business automation should make information easier to manage, not create unnecessary copies of it.

Whether a workflow is transferring customer details, updating business records, or connecting internal systems, businesses should be able to decide what information needs to be retained.

Controlling data storage for specific Flows in integration logs makes it possible to process and transfer information without automatically keeping a copy of the processed data in those logs.

Because moving data between systems and storing that data are two different things, and businesses should have control over both.