To use the Surveys API with Discourse you will authenticate with your GHL API credentials and obtain an access token with the scope socialplanner/post.write
Discourse authentication uses your site API key and secret or OAuth2 depending on setup to authorize actions. Store credentials securely in your app connector.
POST /social-media-posting/:locationId/posts; PUT /social-media-posting/:locationId/posts/:id; DELETE /social-media-posting/:locationId/posts/:id; PATCH /social-media-posting/:locationId/posts/:id
Trigger: A survey response is submitted via Surveys API
Action: Create a new post in Discourse with the response content
POST /social-media-posting/:locationId/posts
locationId, content, title, tags
Trigger: survey update or flag changes
Action: Update an existing Discourse post via PUT
PUT /social-media-posting/:locationId/posts/:id
locationId, id, content
Trigger: survey closed or archived
Action: Delete a Discourse post via DELETE
DELETE /social-media-posting/:locationId/posts/:id
locationId, id
Zero code automation to post survey results to Discourse
Drag and drop workflows with built in endpoints and triggers
Rapid setup that scales as your surveys grow
This section covers endpoints, triggers, actions, and data fields used to connect Surveys API to Discourse
A specific URL path and HTTP method used to perform an action on a service
An event that starts an automation in the integration
A task performed by the integration in response to a trigger
An identifier for a specific Discourse location or channel
Automatically post top survey results every week to a chosen Discourse topic to spark discussion
Create threads with new responses and invite discussion in real time
Summarize survey results and post as an update in a dedicated Discourse category
Obtain required API keys and grant permissions to both services
Configure what events trigger posts and what content to include
Run tests in a sandbox and then enable the workflow
No code is required to get started. You will set up a connection between Surveys API and Discourse using the app connector and configure triggers and actions through prompts. The built in endpoints handle the heavy lifting so you can automate posts without writing code. If you prefer, you can customize content fields to fit your Discourse topics.
Yes. You can map triggers to multiple Discourse categories or topics by using location IDs and content templates. This allows you to publish posts to different areas of your Discourse community based on the source survey or response type. Review permissions to ensure posting rights for each category.
Authentication leverages your GHL API credentials for the Surveys API and standard Discourse authentication. You will generate an access token with the necessary scopes and configure secure storage in the app connector. No code changes are required for typical setups.
Rate limits depend on both Surveys API and Discourse. The integration will queue requests and gracefully back off when limits are approached. If needed, you can adjust the trigger frequency and batch sizes to stay within limits.
Yes. You can update an existing Discourse post by targeting its post ID via the PUT endpoint. Be sure to include only the fields you want to update to avoid overwriting other content.
If a survey is deleted or archived, you can configure the workflow to delete or flag related posts in Discourse. This keeps your community posts aligned with current surveys and avoids outdated content.
Activity logs for the integration are available in the app connector dashboard. You can review successful posts, failed attempts, timestamps, and error messages to diagnose issues quickly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
