Key Features
What Is a Credential?
A workflow needs to prove its access rights before it can call an external API or integrate with a resource such as a database or cloud storage. Agentria manages the authentication information required for this as a concept called a Credential.
A Credential refers to any authentication information — API keys, authentication tokens, passwords, certificates, and more — that the system uses to identify users and verify their access rights.
Credential: Authentication for Service Access
Whenever you call an external API (e.g., using a specific Google service) or integrate with databases, cloud storage, or other resources, a valid credential is required.
Without credentials, the system cannot verify access rights — requests may be rejected, or workflows may fail to execute properly.
In other words, credentials are an essential component for securely exchanging data with external services and ensuring the stable operation of automation workflows.
Key Features and Advantages
Security: Manage sensitive information safely without embedding it directly in code, minimizing the risk of security breaches.
Efficiency: Reuse a single credential across multiple workflows, simplifying management and maintenance.
Organized Management: Manage credentials on a project level to clearly define access permissions per service and prevent privilege misuse.
Learn More
Agentria provides a built-in credential management feature that allows users to easily register, edit, and delete credentials through an intuitive interface.
This enables developers to focus on workflow design and automation without getting tangled in complex security configurations.
If you’d like to learn how to set up credentials and integrate external services in a real project, refer to the following guides and node examples:
Frequently Asked Questions
What is a Credential?
A Credential in Agentria is authentication information required to securely access external services or resources. API keys, authentication tokens, passwords, and certificates all fall under credentials, and the system uses this information to identify users and verify their access rights.
When should you use a Credential?
You need a Credential whenever you build a workflow that calls an external API or integrates with resources such as databases or cloud storage. Without a valid credential, the system cannot verify access rights, so requests may be rejected or the workflow may fail to run properly.
How are Credentials managed?
Credentials are registered, edited, and deleted at the project level, and once registered, a single credential can be reused across multiple workflows. Because sensitive information is stored separately instead of being written directly into code, this reduces the risk of security incidents and lets you clearly separate access permissions by service.
How do Credentials work with nodes?
Nodes that integrate with external services, such as the Gmail node or Slack node, use a registered credential for authentication. Each node requires a different type of credential, so register the credential first by following that service's credential guide before building the workflow.