To connect Zoodealio to Surveys API, obtain OAuth credentials and grant Zoodealio the socialplanner/post.write scope to manage posts.
Create or verify a Zoodealio app key and configure it to securely authenticate against the Surveys API.
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 user schedules a post in Zoodealio, which creates a new post via POST to the Surveys API.
Actions: POST to /social-media-posting/:locationId/posts; set scheduling parameters for timing and visibility.
Endpoint used: POST /social-media-posting/:locationId/posts
Key fields: locationId, content, media, schedule_time, visibility
Trigger: Edit or revise a post in Zoodealio; Zoodealio sends PUT to update the post.
Actions: PUT /social-media-posting/:locationId/posts/:id to update; PATCH for partial changes.
Endpoint used: PUT /social-media-posting/:locationId/posts/:id
Key fields: id, locationId, content, media, schedule_time
Trigger: Post no longer needed; remove via Zoodealio when status changes.
Actions: DELETE /social-media-posting/:locationId/posts/:id
Endpoint used: DELETE /social-media-posting/:locationId/posts/:id
Key fields: id, locationId
Automate posting workflows without writing code and reduce manual steps.
Centralize content control so all posts follow a consistent schedule across platforms.
Rapid setup with pre-built endpoints and triggers for faster go-live.
This glossary covers endpoints, triggers, actions, and fields used in the Zoodealio and Surveys API integration within the GHL workflow.
Application Programming Interface: a defined set of rules that lets Zoodealio talk to the Surveys API.
A specific URL path and HTTP method used to perform an action in the Surveys API.
Process to verify identity and grant access to the Surveys API from Zoodealio.
A callback URL that the Surveys API uses to send real-time updates to Zoodealio.
Draft posts in Zoodealio and push them to the Surveys API on a schedule to maintain consistency.
Pull engagement data from Surveys API and adjust future Zoodealio posts for better results.
Coordinate messages across networks via Zoodealio and the Surveys API for a unified campaign.
Register Zoodealio in the Surveys API developer console and generate a client ID and secret.
Ensure the scope includes socialplanner/post.write and set redirect URI to Zoodealio.
Use a test post to confirm create, update, and delete actions succeed.
To connect Zoodealio to the Surveys API, create an app in Zoodealio and obtain OAuth credentials from the Surveys API. Grant Zoodealio the socialplanner/post.write scope to manage posts. Authorize the connection using the standard OAuth flow. Two-way communication ensures posts are created with the correct metadata. In practice, you can start by testing the POST endpoint to verify that new posts are created in Surveys API when you schedule from Zoodealio.
You need a client ID and client secret issued by the Surveys API. Store these securely in Zoodealio and configure the redirect URI to your app. Use token refresh as needed to maintain a valid session. Always apply the principle of least privilege by only requesting the socialplanner/post.write scope.
The primary endpoints are POST /social-media-posting/:locationId/posts to create, PUT /social-media-posting/:locationId/posts/:id to update, PATCH /social-media-posting/:locationId/posts/:id for partial updates, and DELETE /social-media-posting/:locationId/posts/:id to remove posts. These endpoints cover typical create, update, and delete workflows for social content.
No extensive coding is required. The integration is designed for no-code or low-code setups within Zoodealio. You configure OAuth credentials, set the endpoint paths, and map fields like locationId and content. Advanced users can add custom triggers and conditional logic if needed.
Use a test environment or sandbox in Surveys API to simulate post creation, updates, and deletions. Create a sample post in Zoodealio, run through the flow, and verify the corresponding data appears and changes propagate in Surveys API. Check logs for any errors and adjust field mappings accordingly.
If a publish attempt fails, review the HTTP response and error message, verify authentication, endpoint paths, and required fields. Retry the action after correcting any issues. Implement retry logic and alerts so failed posts are surfaced and retried automatically where appropriate.
Yes. If you delete a post in Zoodealio, you can configure the workflow to call DELETE on the Surveys API to remove the corresponding entry. Ensure you handle ID mapping correctly so the intended post is removed and not other records.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
