Skip to main content

Hootsuite Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Hootsuite location.
hootsuite_api.png

Hootsuite

Create a Hootsuite Destination​

  1. Click the + icon on the Nexset that will be sent to the Hootsuite destination, and select the Send to Destination option from the menu.

  2. Select the Hootsuite connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Hootsuite organization, and click Next; or, create a new Hootsuite credential for use in this flow.

  3. In Nexla, Hootsuite destinations can be created using pre-built endpoint templates, which expedite destination setup for common Hootsuite endpoints. Each template is designed specifically for the corresponding Hootsuite endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Hootsuite destinations can also be configured manually, allowing you to send data to Hootsuite endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Hootsuite endpoints. Each template is designed specifically for the corresponding Hootsuite endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Member

    Creates a member in a Hootsuite organization. Requires organization manage members permission.

    • This endpoint automatically creates a new member in your Hootsuite organization using data from your Nexset. No additional configuration is required beyond selecting this endpoint template.
    • The endpoint uses POST requests to https://platform.hootsuite.com/v1/members. The endpoint URL is automatically constructed based on the Hootsuite API base URL.
    • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the member data to create.
    • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to create a member. If you need to create multiple members, you can send multiple records, but each will be processed as a separate request.
    • This endpoint automatically creates a data source to track the responses received from the Hootsuite API after each call.

    The request body must be properly formatted JSON that matches the Hootsuite API specification for creating members. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. This endpoint requires organization manage members permission, so your OAuth2 credentials must have the appropriate permissions. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. This endpoint automatically creates a data source to track creation responses. For detailed information about creating members, including required fields, field names, and request formats, see the Hootsuite API documentation.

    Add member to team

    Adds a member to a team.

    • Enter the organization ID in the organizationId field. This should be the unique identifier for the Hootsuite organization that contains the team you want to add the member to.
    • Enter the team ID in the teamId field. This should be the unique identifier for the team you want to add the member to.
    • Enter the member ID in the memberId field. This should be the unique identifier for the member you want to add to the team.
    • The endpoint uses POST requests to https://platform.hootsuite.com/v1/organizations/{organization_id}/teams/{team_id}/members/{member_id} where {organization_id} is the organizationId you provide, {team_id} is the teamId you provide, and {member_id} is the memberId you provide. The endpoint URL is automatically constructed based on the Hootsuite API base URL and all the path parameters.
    • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to add a member to a team. If you need to add multiple members to teams, you can send multiple records, but each will be processed as a separate request.
    • This endpoint does not automatically create a data source to track the responses received from the Hootsuite API after each call.

    The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. You must provide the organization ID, team ID, and member ID to add a member to a team. The member must already exist in the organization before they can be added to a team. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about adding members to teams, including required fields and request formats, see the Hootsuite API documentation.

Configure Manually​

Hootsuite destinations can be manually configured to send data to any valid Hootsuite API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Hootsuite destinations, such as destinations that use custom request headers, different HTTP methods, or custom data formatting.

Content Format​

  1. Select the format in which the Nexset data will be sent to the Hootsuite API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Hootsuite API typically uses JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the Hootsuite API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Hootsuite API endpoints typically follow the pattern https://platform.hootsuite.com/v1/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. For detailed information about Hootsuite API endpoints and available APIs, see the Hootsuite API documentation.