ActionOuraUpdated September 2026
How do I fetch my Oura profile?
Short answer: You can get oura profile in Oura by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Oura Get Oura Profile action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
ID id | string | Required | ID |
Sample request
{"id": "{{trigger.id}}"}
Returns
{}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Oura Profile.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Oura Profile.
What does the Get Oura Profile action do in Oura?
Returns the connected user's Oura profile — name, age, weight, biological-sex. For personalised-automation workflows that adjust based on user characteristics.
What inputs does Get Oura Profile require?
Required: ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Oura returns an error?
The run history shows the failed step with its input and the error message Oura returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Get Oura Profile support batch operations?
Run Get Oura Profile inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Oura's rate limits.
More actions