Hootsuite
Turn orders and customer changes into the right Hootsuite audiences and campaigns, with a person approving what goes out.
12 ways to read.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Hootsuite, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- List message review history
message_history.listRead
Example flow
- Hootsuite · List message review history
message_history.listDone - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Hootsuite.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Hootsuite
- Hootsuite's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
Read Hootsuite organisations, teams, social profiles, scheduled and sent messages, approval history and media status. Read-only; nothing is scheduled or published.
Hootsuite API docs- Source actions
- 12
- Data types
- 9
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
me1
- Get authorised memberSource
Get the authorising member's ID, status, language and time zone.
media1
- Get media statusSource
Get an uploaded media item's processing state and time-limited download URL.
message history1
- List message review historySource
List a message's approval and publishing actions (create, approve, reject, schedule, send).
messages2
- Get messageSource
Get one outbound message's text, state, schedule and published post link.
- List messagesSource
List outbound messages (scheduled, pending approval, sent or failed) in a time window of up to 4 weeks, sorted by scheduled send time.
organizations1
- List organisationsSource
List the organisations the authorising member belongs to.
social profile teams1
- List social profile teamsSource
List the IDs of teams with access to a social profile.
social profiles2
- Get social profileSource
Get one social profile's network, username, owner and connection state.
- List social profilesSource
List the social profiles the authorising member can access.
team social profiles1
- List team social profilesSource
List the IDs of an organisation team's social profiles.
teams2
- Get teamSource
Get a team's name and audit fields.
- List organisation teamsSource
List an organisation's teams.
Access and limits
- Authentication
- Hootsuite OAuth app with a rotating refresh token
- Plans and access
- Hootsuite accounts whose users can authorise an approved Hootsuite developer app. Plan eligibility for API access is set by Hootsuite. Requires an approved Hootsuite developer account and an OAuth app (client ID and secret). The token acts as the authorising member and sees only the profiles, teams and messages that member can access in the dashboard.
- Test environment
- Hootsuite has no sandbox; use a test organisation and social profiles you own.
- Rate limits
- 20 requests a second and 100,000 calls a day per client. Responses carry X-Account-Quota, X-Account-Quota-Used and X-Account-Rate-Limit-Requests-Remaining headers. HTTP 429 is backed off.
- Pagination
- Messages use limit (max 100) and cursor = metadata.cursor.next. Profiles, organisations and teams are single lists.
- Provider events
- Hootsuite message webhooks (state changes) are set per message when scheduling; Nexra does not schedule messages. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Read-only. Hootsuite's REST API has no draft state: POST /v1/messages schedules a real message that publishes at scheduledSendTime (or immediately with send-now review messages), so scheduling, sending, approving, rejecting and deleting messages are intentionally not implemented.
- List messages requires a start and end time no more than 4 weeks apart and returns messages sorted by scheduled send time; there is no updated-since filter.
- The socialProfileIds filter is documented as a single integer, so List messages filters by one social profile at a time.
- Member email, name and bio, team member lists, permissions and SCIM user data are not read. Message targeting, privacy, geolocation and webhook URLs are not mapped.
- Media upload (POST /v1/media) is an engine gap and is not implemented; Get media status returns the time-limited download URL only.
- TikTok, YouTube and Bluesky are not supported by Hootsuite's publishing API, so their messages may not appear.
- Organisation and team reads need the member to belong to an organisation; personal accounts return only their own profiles.
Developer reference
- Create the Hootsuite credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Hootsuite, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/hootsuite and the Connections API.