Authenticate the Users API to Notta using OAuth 2.0 with your API credentials. Use the provided scope: socialplanner/tag.readonly to grant read-only access to tag data. Store tokens securely and rotate them every 90 days.
Notta requires a secure OAuth flow to authorize access to the Users API. Save client ID, client secret, and redirect URIs, and confirm user consent before operations begin.
Endpoints used: GET /social-media-posting/:locationId/tags; POST /social-media-posting/:locationId/tags/details; socialplanner/statistics.readonly; POST /social-media-posting/statistics
Trigger: When a new post is published in Notta, fetch the current tags from the Users API to attach relevant tags.
Actions: Update post tags in Notta, generate analytics events, and store tag mappings.
GET /social-media-posting/:locationId/tags
locationId, tagId, tagName
Trigger: Updates to tag details in the Users API trigger a sync to Notta using the /tags/details endpoint.
Actions: Push tag details into Notta tags, update attributes, and refresh dashboards.
POST /social-media-posting/:locationId/tags/details
locationId, tagDetails
Trigger: Daily or hourly statistics pull from the Users API.
Actions: Store statistics in Notta, power dashboards, and generate insights.
GET socialplanner/statistics.readonly
locationId, timestamp, metricName
No-code, drag-and-drop style integration between Notta and the Users API enables fast, code-free automation.
Automatic data syncing reduces manual entry and ensures up-to-date tags and stats.
Secure, scalable authentication keeps data safe while you scale Notta usage.
Key elements include endpoints, authentication, triggers, actions, and data flows between Notta and the Users API to automate tagging and reporting.
A programmable interface that lets Notta access the Users API data and operations.
A standard authorization framework enabling Notta to obtain access tokens securely for the Users API.
A lightweight HTTP callback that Notta uses to receive real-time updates from the Users API.
The maximum number of API calls allowed in a given time window to protect the API from abuse.
Automatically extract relevant tags from Notta posts using the Users API and apply them for improved discovery and engagement.
Pull live metrics from the Users API to power dashboards in Notta and share insights with teams.
Create Notta triggers that automatically adjust tags when the Users API data changes.
In the GHL developer portal, generate a client ID and secret, then configure Notta with these credentials.
Authorize access with the socialplanner/tag.readonly scope and approve the Notta app for the required data.
Test in a staging environment, verify data flows, then switch to production.
The Notta + Users API integration lets you access and manage tag data and statistics directly from Notta. This enables automation of tagging workflows and faster decision-making. This guide helps you authenticate, configure endpoints, and implement workflows without coding.
You can read tag lists and related metadata via socialplanner/tag.readonly, including tag names, IDs, and associated posts. For deeper insights, use endpoints such as GET /social-media-posting/:locationId/tags and GET socialplanner/statistics.readonly to retrieve statistics. POST /social-media-posting/statistics can be used to submit aggregated data as needed.
Use OAuth 2.0 flow with a client ID/secret and a redirect URI. Ensure the Notta app is granted consent to access the required scopes. Store tokens securely and rotate them regularly. If refresh tokens are available, implement automatic token refresh.
Basic syncing typically leverages GET /social-media-posting/:locationId/tags and GET socialplanner/statistics.readonly for read data, with updates via POST /social-media-posting/:locationId/tags/details and POST /social-media-posting/statistics for write or aggregated data.
Data can be refreshed in real time or on a schedule. Notta can be configured to pull updates hourly, every 15 minutes, or at another interval depending on your needs and API rate limits.
The integration is subject to the API’s rate limits. If you reach limits, implement exponential backoff and retries, and consider caching frequently requested data. Plan request windows to avoid bursts.
Common issues include invalid credentials, misconfigured redirect URIs, missing scopes, or incorrect endpoint paths. Check Notta’s admin console logs, reauthorize the app, verify credentials, and ensure the correct endpoints are used.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
