Authorize your account
Open Connections → API connections and choose Connect X. Authorize profile reading, post reading/writing and offline access. NoriaFlow stores both access and refresh tokens encrypted and renews the access token when needed. Each account becomes a separate connection that you can select per node.
The server must have an X OAuth application configured. If the control is
unavailable, its administrator must set X_CLIENT_ID, X_CLIENT_SECRET for a
confidential app, and X_REDIRECT_URI. Register the exact callback URL in the
X Developer Console:
https://YOUR_API_HOST/api/v1/api-connections/x/oauth/callback
For advanced use, you can instead store a manually obtained token as an X API connection. Writing requires a user OAuth 2.0 access token, not an app-only bearer token. Manually entered tokens are not automatically refreshed; replace them before they expire.
Available actions
| Action | Purpose |
|---|---|
| Read Post | Read a post by ID |
| Get User | Look up a username |
| Get My Profile | Identify the connected user |
| Create Post | Publish text |
| Reply to Post | Reply to an existing post |
| Delete Post | Delete a post belonging to the connected user |
Use Manual trigger → Get My Profile to verify the connection. Then configure your automation and run its test before publishing. A simulated write does not publish a real post or establish that the account has live write permission.
Access requirements
Your X app needs API access to the requested endpoints. X enforces permissions, usage allowances, posting limits and reply restrictions independently of NoriaFlow. An expired or revoked authorization must be reconnected. A successful connection does not guarantee that every API operation is available.
These nodes implement REST actions. Media uploads, streaming and native event subscriptions are not included. See the official post API and OAuth 2.0 guide.