Objects

How Lead360 helps

Lead360 Objects models structured business records that do not fit standard contacts, appointments, or opportunities. An object can define its own fields and relationships so teams can capture domain-specific information without forcing it into notes or inconsistent tags.

When to use this area

Use Objects when the business needs a repeatable record type with multiple fields, lifecycle, and relationships.

Before you begin

• Define the real-world entity, owner, lifecycle, and required relationships.
• Confirm a standard Lead360 record does not already represent it.
• Design stable fields and identifiers before importing data or building automations.

Model the record first

1. Define the real-world item the object represents and who owns it.
2. Add only fields needed for operations, reporting, or automation.
3. Choose field types and required rules before importing records.
4. Define relationships to contacts, opportunities, or other objects.

Build and verify

1. Create the object and a small sample of records.
2. Confirm list, detail, search, permissions, and relationship behavior.
3. Test forms, automations, integrations, and reports that use it.
4. Document the schema before broader rollout.

Protect live data

Changing field types, relationships, or deleting an object can affect records and workflows. Export or verify dependencies and require approval before destructive changes.

Use Ask360 here

Ask360 can explain authorized object schemas, relationships, and dependencies and prepare one reviewed object or field definition when supported. It never deletes an object, changes a populated field type, imports records, or rewrites relationships from this Help flow.

Confirm the result

A completed Objects workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

• Create representative records and relationships.
• Test permissions, forms, imports, filters, and automations.
• Confirm deletion and retention behavior for related records.

Troubleshooting

The object duplicates another data model

Pause new records and compare ownership, identifiers, relationships, and downstream dependencies before consolidating.

Automation cannot find an object field

Check the published object definition, field key, data type, scope, and operation support.