Agorapulse

Contact your Agorapulse account manager directly — by email or via your account dashboard support channel — and confirm that your account subscription includes API access. Provide your use case (custom Bubble moderation interface) and ask for: 1. Confirmation that API access is available on your plan 2. OAuth client_id and client_secret for your application 3. Documentation for the specific API endpoints available to your account (inbox, scheduling, profile management) 4. Your account's rate limits per API endpoint Do not attempt to find Agorapulse API credentials through a self-serve developer portal — there is no public portal. Building the integration before receiving confirmed credentials and documentation from Agorapulse support will result in 401 or 403 errors regardless of implementation. Once you receive your client_id and client_secret, store them securely in a password manager. You'll enter them as Private parameters in Bubble's API Connector — they should never appear in your Bubble app's visible interface, in Bubble database fields, or in any code visible to users. Also confirm the token lifespan with your account manager — this determines how frequently your scheduled token refresh Backend Workflow needs to run. Token lifespans are not publicly documented for Agorapulse and vary by account configuration.

In Bubble's Data tab, create a new data type called 'AgorapulseToken'. Add these fields: - access_token (text) — the current Bearer token for API calls - expires_at (date) — when the current token expires - last_refreshed (date) — for monitoring the refresh schedule Set privacy rules on this data type immediately: go to Data tab → Privacy → AgorapulseToken → add a rule that prevents any users from reading AgorapulseToken records through Bubble's Data API. Only server-side Backend Workflows should interact with this data type. Now go to Backend Workflows (requires a paid Bubble plan). Create a new API workflow named 'ExchangeAgorapulseToken'. This workflow should NOT be user-triggered — it runs manually from an admin page or on a schedule. In this workflow, configure an API Connector call (named 'Get Agorapulse Token') first: - Method: POST - URL: https://app.agorapulse.com/api/oauth/token - Body type: Form parameters URL-encoded - Parameters: - grant_type: client_credentials (static value) - client_id: <private: your_client_id> - client_secret: <private: your_client_secret> In the ExchangeAgorapulseToken Backend Workflow: - Step 1: Call 'Get Agorapulse Token' API - Step 2: Create or modify AgorapulseToken record: set access_token = token API result's access_token, expires_at = Current date/time + [verified token lifespan], last_refreshed = Current date/time Run this Backend Workflow manually once to create the initial token. Confirm the AgorapulseToken record exists in Bubble's Data tab with a valid access_token value.

1{
2  "token_exchange_call": {
3    "method": "POST",
4    "url": "https://app.agorapulse.com/api/oauth/token",
5    "body_type": "Form parameters URL-encoded",
6    "parameters": {
7      "grant_type": "client_credentials",
8      "client_id": "<private: your_client_id>",
9      "client_secret": "<private: your_client_secret>"
10    }
11  },
12  "expected_response": {
13    "access_token": "eyJhbGciOiJSUzI1Ni...",
14    "token_type": "Bearer",
15    "expires_in": 3600
16  },
17  "data_type": {
18    "name": "AgorapulseToken",
19    "fields": {
20      "access_token": "text",
21      "expires_at": "date",
22      "last_refreshed": "date"
23    },
24    "privacy": "No users can read via Data API"
25  }
26}

Go to Plugins → Add plugins → search 'API Connector' → Install (by Bubble, free). Click 'Add another API'. Name it 'Agorapulse'. Base URL: https://app.agorapulse.com/api Add a shared header: - Name: Authorization - Value: Bearer <dynamic: access_token> - This makes 'access_token' a dynamic parameter that must be provided with each API call The Private checkbox on dynamic parameters works differently from static ones. In each individual API call, when you add the access_token parameter, mark it Private at the call level. This ensures that even though the token value is sourced dynamically from the database at runtime, Bubble treats it as a server-side-only value. Add a second shared header: - Name: Content-Type - Value: application/json Save. Now in every Bubble workflow that uses an Agorapulse API action, you'll set access_token = 'Do a search for AgorapulseToken:first item's access_token'. This pattern keeps the token out of the browser. The workflow reads the token from the database server-side, passes it to the API Connector as a Private parameter, and the API call goes from Bubble's server to Agorapulse's server. The browser never sees the token value.

1{
2  "api_name": "Agorapulse",
3  "base_url": "https://app.agorapulse.com/api",
4  "shared_headers": {
5    "Authorization": "Bearer <dynamic: access_token (Private per call)>",
6    "Content-Type": "application/json"
7  },
8  "workflow_token_sourcing": "access_token = Do a search for AgorapulseToken > First item > access_token"
9}

Add the inbox read call: - Name: Get Inbox Items - Method: GET - Path: /inbox (verify the exact endpoint path with Agorapulse's documentation provided by your account manager) - Parameters: status (dynamic: filter by unanswered, in_progress, done), platform (optional: filter by specific social network) - Use as: Data - Initialize with access_token from your stored AgorapulseToken and test parameter values After successful initialization, Bubble detects the response fields. Agorapulse inbox items typically include: id, text (message content), sender (nested object with name and social handle), platform, created_at, and status. On your page, add a repeating group: - Type of content: the API response type for Get Inbox Items - Data source: Get Inbox Items API call with access_token = search AgorapulseToken:first item's access_token, status = 'unanswered' Inside the repeating group, add: - Text element: Current cell's sender's name - Text element: Current cell's text (with max character display — use Bubble's 'truncate after 120 characters' format) - Text element: Current cell's platform (display as icon using a Conditional rule: when this cell's platform is 'INSTAGRAM', set icon to Instagram image; when 'TWITTER', set to Twitter/X image; etc.) - Text element: Current cell's created_at formatted as relative time ('2 hours ago') - Button: 'Reply' — triggers the reply workflow - Button: 'Mark as Done' — triggers a status update call Add filter buttons above the repeating group (All / Unanswered / In Progress / Done) that update a custom state 'InboxStatus' and trigger a re-fetch of the inbox with the new status filter.

1{
2  "method": "GET",
3  "url": "https://app.agorapulse.com/api/inbox",
4  "headers": {
5    "Authorization": "Bearer <dynamic: access_token (Private)>"
6  },
7  "query_parameters": {
8    "status": "<dynamic: status_filter>"
9  },
10  "example_response": {
11    "data": [
12      {
13        "id": "inbox_item_abc123",
14        "text": "Love your product! When does the new feature launch?",
15        "sender": {
16          "name": "Jane Smith",
17          "handle": "janesmith"
18        },
19        "platform": "INSTAGRAM",
20        "created_at": "2026-07-08T14:22:00Z",
21        "status": "unanswered"
22      }
23    ],
24    "meta": {
25      "total": 47,
26      "page": 1
27    }
28  }
29}

Add the reply POST call: - Name: Post Reply - Method: POST - Path: /inbox/{item_id}/reply (verify exact path with Agorapulse documentation) - Body type: JSON - Body: { "text": "<dynamic: reply_text>" } - Use as: Action - Initialize with access_token, a real inbox item ID from your test data, and a test reply text Warning from the brief: reply actions modify live social content in real-time. A mistaken reply to a comment goes public immediately. Always add a confirmation dialog before executing reply workflows. Build the reply flow: 1. User clicks Reply button on an inbox item in the repeating group 2. A popup opens showing: the original message (Current cell's text), a multiline text input for the reply, a 'Send Reply' button, and a 'Cancel' button 3. On 'Send Reply' click: show a second confirmation popup: 'Confirm: post this reply publicly to [sender name] on [platform]? This cannot be undone.' with Confirm and Cancel buttons 4. On Confirm: call Agorapulse 'Post Reply' API with access_token = search AgorapulseToken:first item's access_token, item_id = the inbox item's ID from the original repeating group row, reply_text = the reply text input's value 5. After successful reply: close all popups, show a toast notification 'Reply sent to [sender name]', update the inbox item's status to 'done' (call a separate status update API action or optimistically update the Bubble custom state) RapidDev's team builds custom community management tools in Bubble — for integrations with multiple social platforms and custom CRM tagging workflows, book a free scoping call at rapidevelopers.com/contact.

1{
2  "reply_call": {
3    "method": "POST",
4    "url": "https://app.agorapulse.com/api/inbox/<item_id>/reply",
5    "headers": {
6      "Authorization": "Bearer <dynamic: access_token (Private)>",
7      "Content-Type": "application/json"
8    },
9    "body": {
10      "text": "<dynamic: reply_text>"
11    }
12  },
13  "workflow_sequence": [
14    "1. Reply button click → open Reply Compose popup",
15    "2. Send Reply button → open Confirmation popup",
16    "3. Confirm button → call Post Reply API",
17    "4. Success → close popups, show toast, refresh inbox"
18  ]
19}

The Bearer token obtained via client credentials has a finite lifespan (verify the exact duration with Agorapulse). A scheduled Backend Workflow must refresh the token before it expires for production stability. Create a Backend Workflow named 'RefreshAgorapulseToken'. This workflow: - Step 1: Call the 'Get Agorapulse Token' API (the same token exchange call configured in Step 2) - Step 2: Make changes to the AgorapulseToken record: access_token = new token result's access_token, expires_at = Current date/time + [verified token lifespan], last_refreshed = Current date/time For client credentials flow, there is no refresh_token — you simply exchange client credentials again for a completely new access_token. This is different from Authorization Code flow (like Hootsuite) where a separate refresh_token is used. Set the refresh schedule based on your verified token lifespan. If the lifespan is 1 hour (3600 seconds), schedule the refresh every 50 minutes. If it's 24 hours, every 20 hours. Always schedule it before expiry, not at expiry. Go to Backend Workflows → Recurring events → Add event → select RefreshAgorapulseToken → set interval based on your verified token lifespan. Add a monitoring element to your admin page: display the AgorapulseToken record's expires_at and last_refreshed values. If expires_at is within 1 hour of the current time and last_refreshed is not recent, the refresh is failing — investigate Backend Workflow logs.

1{
2  "refresh_workflow": "RefreshAgorapulseToken",
3  "steps": [
4    "Step 1: Call Get Agorapulse Token API (client_credentials grant — same as initial exchange)",
5    "Step 2: Make changes to AgorapulseToken record: access_token = new value, expires_at = now + lifespan, last_refreshed = now"
6  ],
7  "schedule_note": "Set recurring event interval to 80% of token lifespan (e.g., every 50 min for 1-hour tokens, every 20h for 24-hour tokens)",
8  "admin_monitoring": {
9    "display": ["AgorapulseToken expires_at", "AgorapulseToken last_refreshed"],
10    "alert": "Show warning if expires_at < now + 1 hour AND last_refreshed < now - [interval]"
11  }
12}