Zoho CRM Connected Records: setup and workflows

Use Zoho CRM Connected Records when a business record needs a connected piece of work with its own context. A fictional example is a sales deal that needs an onboarding request for another team. The deal remains the sales context; the request describes the work needed for that customer.

Planning this work for your team? See our Zoho CRM automation and customisation service.

Before configuring anything, check your account's available association controls. Zoho's older FAQ and its Organisation module enhancement announcement describe different scopes. A universal click path would conceal that difference.

Understand Connected Records and ordinary lookups

Start with the business relationship you need. “This contact belongs to this account” and “this deal needs an onboarding request” are different modelling problems.

For the first, review the conventional account/contact relationship. For the second, evaluate a connected request with a clear source record, receiving team, owner, and completion condition. Choose based on the work, rather than the appeal of a feature name.

The accounts versus contacts guide helps establish the customer model before you introduce another record relationship.

Connected Records and Connected Workflows also answer different questions. The association describes the context records share. A workflow describes what should happen when a relevant event occurs. Configure and test the relationship before relying on an automated action.

For reciprocal relationships among contacts or leads, first write down the meaning in each direction. “Advises” and “is advised by” are not interchangeable. Check the available relationship options in your current account; do not assume Connected Records automatically creates every reciprocal relationship you imagine.

Check the current account interface and access

The older FAQ restricts connected additions to Team modules. The Organisation module enhancement announcement explicitly describes Organisation module associations through Module Layout and Connected To configuration.

Treat this as a documentation-scope conflict to resolve in your account. Inspect the live interface and check Zoho's current help docs before concluding that an unavailable option is a bug.

The announcement requires Module Customisation permission. Have an appropriately authorised administrator inspect the layout. Record the source module, intended associated module, and options actually offered.

If an Organisation module does not appear, check access and the applicable layout configuration first. Compare what you see with the enhancement guidance. If it remains unavailable, ask Zoho to confirm availability for your account and provide the observed screen details.

Do not substitute a different module simply to finish setup. That changes the business model and can leave the receiving team working from the wrong context.

Configure the Connected To association

Write a small association plan before editing the layout:

Decision	Fictional example
Business context	The customer deal
Requested work	An onboarding request
Intended association	Request connected to the correct deal
Reviewer	Sales owner and receiving team owner
Verification	Both records identify the intended context

From the relevant Module Layout page, inspect the Connected To field properties and select the intended Organisation modules where the feature is available. The enhancement announcement states a maximum of 30 associated modules per Connected To configuration. Select only the modules your process needs.

Capture the existing configuration before changing it. Review whether the association serves other teams or established work. A narrow pilot is easier to assess than a broad configuration change across unrelated modules.

Save the approved settings and reopen the layout properties. Confirm the selected modules persisted. Configuration that looks correct in an unsaved editor is not evidence that users can create the intended relationship.

For unrelated corrections to existing customer links, use a separate cleanup plan such as contacts under the wrong account.

Create and inspect a connected request

Create a controlled onboarding request using the association options available in the account. Use a clearly identified test deal and include enough context for the receiving owner to understand the work.

Check the request's subject, owner, customer context, and intended source record before saving. Similar deal names can conceal a wrong association, so compare record identifiers.

After saving, inspect the request and the source deal. Verify the relationship from both records using the presentation your account offers. If one side is unavailable or unclear, document the observation and investigate rather than asserting that the relationship passed.

Ask the receiving team to review the saved request through their own permitted view. The administrator's ability to see everything is not a substitute for checking the actual working process.

Keep a separate list of existing tasks or cases that need their customer context repaired. The Tasks guide explains task relationships. For cases, inspect the relevant customer lookup and correct the verified link; do not redefine ordinary cleanup as a connected request.

Add a Connected Workflow

Zoho's Connected Workflows guide describes record-create, record-edit, and field-edit triggers. Actions can create connected records, update them, or notify users.

Choose one event and one intended outcome for the pilot. For example, specify the approved condition that makes an onboarding request necessary and the record that should result. Do not enable a broad edit trigger without deciding what repeated edits should do.

Inspect the current workflow controls and configure the supported trigger, criteria, and action. Verify the association and required input values before enabling the rule.

Test a qualifying event, a nonqualifying event, and a repeated relevant edit. Inspect the resulting record or notification after each. Check whether an existing request should be reused, left alone, or reviewed; do not assume duplicate prevention from the feature name.

If the action updates a field, use the record-update checks to capture original values and verify the result.

Get help with this CRM task

For help with a cross-team CRM handoff, contact zsetup. Include the source and receiving modules, required context and ownership rules. Share redacted examples rather than live customer details or credentials.

Our Zoho CRM automation and customisation service explains the scope we can discuss and how the work is checked.