How do you configure an auto-launched Flow as an Agentforce Action and what are the key design rules?

To use a Flow as an Agentforce Action:

1. Flow type: Must be an Auto-launched Flow (not a Screen Flow). The agent invokes it programmatically without user interaction.
2. Input variables: Define input variables with "Available for input" checked. The variable label and description are surfaced to the LLM — write them in natural language describing what data to pass.
3. Output variables: Define output variables with "Available for output" checked. The agent uses these values in its response or subsequent reasoning steps. Keep outputs focused — return exactly what the agent needs, not the entire record.
4. Error handling: Add Fault paths to all data operations (Get Records, Create Records, etc.) and set an error output variable so the agent can communicate a failure gracefully rather than silently stopping.
5. API Name: The API name of the Flow appears in Agent Builder when you add it as an action — use a clear, descriptive name.
6. Testing: Test the Flow independently in Flow Builder's debug mode before testing it as an agent action to isolate issues. Flows are the most admin-maintainable action type and should be preferred over Apex when the logic can be expressed declaratively.