atlan-workflow-args-secrets-state

Retrieve workflow arguments and credentials securely via Atlan SDK patterns.

4|7|Updated Apr 30, 2025

Search Tags:#workflow #secrets #state-store #credential_guid #runtime-args #atlan-sdk

Ready to run

npx skills add https://github.com/atlanhq/atlan-sample-apps --skill atlan-workflow-args-secrets-state

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: atlan-workflow-args-secrets-state
Source: https://github.com/atlanhq/atlan-sample-apps/tree/main/.agents/skills/atlan-workflow-args-secrets-state
Command: npx skills add https://github.com/atlanhq/atlan-sample-apps --skill atlan-workflow-args-secrets-state

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill ensures secure, consistent retrieval and handling of workflow arguments and credentials using Atlan SDK patterns, preventing raw secret exposure and keeping runtime state synchronized across activities.

Core Features & Use Cases

Credential handling: Use credential_guid to fetch credentials securely without embedding secrets in workflow args.
Args normalization: Load and normalize workflow arguments through SDK-supported state paths.
State persistence: Persist and propagate workflow state via SDK-compatible state store APIs across activities and workflows.
Use Case: When a long-running workflow handles secrets and state, this skill coordinates args, credentials, and state updates.

Quick Start

Run the skill to enable secure retrieval of a credential via credential_guid and update the workflow state in the current session.

Frequently Asked Questions about atlan-workflow-args-secrets-state

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I securely handle credentials in Atlan workflows without exposing secrets?▼

Secure credential handling in Atlan workflows uses credential_guid to fetch credentials through SDK patterns, avoiding raw secret exposure. The skill retrieves credentials safely without embedding secrets directly in workflow arguments or state.

How do I normalize and load workflow arguments using Atlan SDK?▼

Workflow arguments are normalized and loaded through SDK-supported state paths. This skill applies SDK patterns to retrieve and structure runtime arguments consistently across activities and execution environments.

Can I persist workflow state across multiple activities and executions?▼

Yes. This skill persists and propagates workflow state via SDK-compatible state store APIs, keeping runtime state synchronized across activities and long-running workflows without losing data between executions.

What's the best way to coordinate secrets, args, and state in long-running workflows?▼

Coordinate secrets, args, and state by using credential_guid for secure credential retrieval, SDK state paths for argument normalization, and state store APIs for persistence. This approach prevents raw secret exposure while maintaining state consistency.

When should I use credential_guid instead of embedding credentials directly in workflow arguments?▼

Always use credential_guid to retrieve credentials rather than embedding them in workflow arguments. This prevents secrets from persisting in logs, state stores, or being accidentally exposed across execution environments.