All connectors
Implemented
Marketing & advertising
Hootsuite logo

Hootsuite

Read Hootsuite organisations, teams, social profiles, scheduled and sent messages, approval history and media status. Read-only; nothing is scheduled or published.

Report on what is scheduled, awaiting approval or published across Hootsuite social profiles, and sync profile and team structure into marketing operations flows.

Source actions

12

Destination actions

0

Data types

9

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

me
  • Get authorised member
    Source

    Get the authorising member's ID, status, language and time zone.

    me.get
media
  • Get media status
    Source

    Get an uploaded media item's processing state and time-limited download URL.

    media.get
message history
  • List message review history
    Source

    List a message's approval and publishing actions (create, approve, reject, schedule, send).

    message_history.list
messages
  • Get message
    Source

    Get one outbound message's text, state, schedule and published post link.

    messages.get
  • List messages
    Source

    List outbound messages (scheduled, pending approval, sent or failed) in a time window of up to 4 weeks, sorted by scheduled send time.

    messages.list
organizations
  • List organisations
    Source

    List the organisations the authorising member belongs to.

    organizations.list
social profile teams
  • List social profile teams
    Source

    List the IDs of teams with access to a social profile.

    social_profile_teams.list
social profiles
  • Get social profile
    Source

    Get one social profile's network, username, owner and connection state.

    social_profiles.get
  • List social profiles
    Source

    List the social profiles the authorising member can access.

    social_profiles.list
team social profiles
  • List team social profiles
    Source

    List the IDs of an organisation team's social profiles.

    team_social_profiles.list
teams
  • Get team
    Source

    Get a team's name and audit fields.

    teams.get
  • List organisation teams
    Source

    List an organisation's teams.

    teams.list

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. Nexra event triggers are not yet available; flows run on demand or on a schedule.

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

  1. Create the Hootsuite credentials described above with the narrowest permissions your flows need.
  2. 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
  3. 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.