Generate JWT Token
Use this action when a later step needs a signed token to authenticate a request to AutoTalk's own /v1 API.
Best for
- Authenticating a later request to AutoTalk's
/v1API (for example, an AutoTalk MCP-connect step) - Passing the token to AutoTalk's API via the
x-jwt-token(orx-auth-token) header — it is signed with AutoTalk'sJWT_SECRETand is not verifiable by arbitrary third-party systems - Restricting access with a short validity window
Main fields
| Field | What it does |
|---|---|
| Advanced mode | Unlocks the Duration and Allowed IPs options. Duration only takes effect when this is on (otherwise the token uses the default 300-second lifetime). Allowed IPs are never silently dropped: providing an IP list without Advanced mode is rejected with an error rather than ignored |
| JWT Duration (seconds) | How long the token stays valid, in seconds. Defaults to 300 (5 minutes) and is capped at 86400 (24 hours). Only applied when Advanced mode is on |
| Allowed IPs | Restricts the token to specific IP addresses. Only applied when Advanced mode is on — and providing IPs without Advanced mode is rejected (the restriction is enforced, never silently lost) |
What later steps can use
The token is available at:
step(N).jwt
Tips
- Keep the duration short unless you have a strong reason not to.
- Only use IP restrictions when the receiving system has a stable IP range.
- Treat the generated token as sensitive data in later steps.