Overview

The Attributes (or Attributes) are the fundamental blocks of information within Nuvia. They define the characteristics and properties of platform objects, such as People, Companies and Deals, ensuring that all data are standardized, consistent and reused in lists, reports, automations and integrations.

What is an Attribute?

An Attribute represents an information field that describes a specific property of an object.

Examples:

A Person may have attributes such as Name, Email, and Job Title.
A Company may have attributes like Company Name, Industry, and Size.

Attributes can be of two main types:

System Attributes: Standard attributes created by Nuvia and used across the entire platform.
Custom Attributes: Attributes created by users to adapt the platform to their specific business needs.

How it works

Each attribute has a set of parameters that define its structure, behavior, and data source. These parameters ensure data integrity, consistency, and clarity across all objects.

Parameter	Description	Example
Slug	Unique identifier code for the attribute.	`email_corporativo`
Attribute Name	Visible and standardized name.	“Corporate Email”
Format	Accepted data type.	Text, Number, URL, Currency, Date, Select, etc.
Constraints	Rules applied (Unique, Required, Immutable).	Email = Unique
Type	Source of the attribute (System or Custom).	Custom
Data Source	How the value is generated (User input, System default, Provider-enriched, AI-generated).	Created at → System default
Relationship	Defines relationships between objects (1:1, 1:N, N:M).	A Company may have multiple People
Object	Entity to which the attribute belongs.	People, Company, or Deal

Slug

The Slug is the attribute’s unique identifier code. It allows the platform to recognize each field internally and ensures no duplicates exist.

Example:

Visible name: “Email Address”
Slug: email

Attribute Name

This is the visible name of the attribute — how it appears to users in Nuvia. It should be clear, descriptive, and follow naming conventions that make identification easy.

Examples:

“Full Name”
“Closing Date”
“Company Industry”

Format

Defines the data type accepted by the attribute.
It ensures that each field stores only the correct type of information, maintaining consistency across data entries.

Main formats:

Text: Free text (names, descriptions)
Number: Numeric values
Date / Timestamp: Dates and times
Select / Multi-select: Predefined options
Currency: Monetary values
URL: Website addresses
User / Relationship: Links to other objects

Example: O atributo “Valor do Deal” utiliza o formato Currency.

Constraints

Constraints are rules that define how an attribute behaves. They help enforce restrictions and preserve data integrity.

Common types:

Unique: Value cannot be duplicated (e.g., email).
Required: Mandatory field.
Immutable: Cannot be changed after creation.

Example: The “Email” attribute for a person must be Unique to avoid duplicate records.

Type

The Type classifies an attribute according to its origin:

System: Created by Nuvia as part of the default configuration.
Custom: Created by an admin user.

Examples:

“Created at” → System
“Departamento interno” → Custom

Data Source

Defines how the attribute’s value is generated or filled in. This parameter helps identify whether the data was manually entered, system-generated, or enriched from an integration.

Main sources:

User input: Entered manually by the user.
System default: Automatically filled by Nuvia.
Enriched: Obtained via integration with external providers.
AI-boosted: Generated or inferred by artificial intelligence.

Example: “Created at” is System default; “Industry” may be Enriched.

Relationship

The Relationship parameter defines how an attribute connects to other objects in Nuvia. It establishes the links between entities such as People, Company, and Deal.

Types of relationships:

1:1 (one-to-one): A Company has one main email.
1:N (one-to-many): A Company can have multiple People.
N:M (many-to-many): A Person can be involved in multiple Deals, and vice versa.

Importante: Relationships are bidirectional — each object “knows” its associations without duplicating attributes.

Object

The Object is the entity that contains the attribute. Each attribute belongs to a specific object type within Nuvia.

Available objects:

People: Attributes related to individuals or contacts.
Company: Attributes related to organizations or businesses.
Deal: Attributes related to transactions or opportunities.

Example: The “Job Title” attribute belongs to People; “Industry” belongs to Company.

FAQ

What are Attributes used for?

To structure, categorize, and connect information within Nuvia in an organized and automated way.

Can I create my own Attributes?

Yes, if you have admin permissions. These are called Custom Attributes.

What is the difference between an Attribute and an Object?

An Attribute is the piece of information (e.g., “Name”), while the Object is the entity that contains it (e.g., People).

What are Relationships?

They define how different objects are connected, such as a person being associated with a company or deal.

Where are Attributes used?

In records, reports, automations, and integrations throughout the Nuvia platform.