Authenticate Zid with the Surveys API using API keys and OAuth scopes to control access securely.
Zid uses OAuth 2.0 to authorize requests; obtain a client ID and secret from your Zid dashboard and grant permission to 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 new survey response is recorded and automatically drafted into a social post in Zid.
Actions: Zid uses POST to publish the drafted post to connected social accounts.
Method path: POST /social-media-posting/:locationId/posts
Key fields: locationId, content, scheduleTime
Trigger: update events in Zid reflect on the corresponding post in Surveys API.
Actions: use PUT to modify the existing post at /social-media-posting/:locationId/posts/:id
Method path: PUT /social-media-posting/:locationId/posts/:id
Key fields: id, locationId, content
Trigger: posts are no longer needed or violate policy.
Actions: call DELETE on /social-media-posting/:locationId/posts/:id to remove the post.
Method path: DELETE /social-media-posting/:locationId/posts/:id
Key fields: id, locationId
No-code automation lets non-developers build workflows without writing code.
Drag-and-drop logic, templates, and triggers accelerate deployment.
Fast ROI with visual builders and reusable components.
This glossary covers the core terms and processes used in the integration between Zid and the Surveys API.
Application Programming Interface — a set of rules that lets applications communicate.
OAuth 2.0 is an authorization framework enabling secure access tokens for apps.
A URL exposed by an API that performs a specific action or data retrieval.
A callback URL that receives real-time data from an external system.
Schedule daily posts powered by new survey responses to keep channels active.
Automatically generate posts when survey answers meet thresholds or trigger events.
Test different post formats to see what resonates with your audience.
In Zid, create an app and obtain client credentials (ID and secret).
Use OAuth 2.0 to request access tokens for the Surveys API.
Map fields between Zid and Surveys API endpoints and start automating posts.
No coding is required for basic connections. Zid provides a visual setup to link Surveys API to post publishing. If you need advanced logic, you can extend with custom rules in Zid. Always start with sandbox testing to validate your flow.
For basic posting you’ll typically use the POST endpoint to create posts, plus PUT or PATCH for updates and DELETE for removal. Ensure locationId and required fields are provided.
OAuth 2.0 grants access tokens after user consent. Your app will request the scopes needed for posting and reading survey data. Tokens should be stored securely and refreshed before expiry.
Yes. Use PUT to update an existing post or PATCH for partial updates, and DELETE to remove a post when it’s no longer needed. These actions can be triggered from Zid automations.
Yes. Zid’s visual builder lets you test connections in a sandbox environment before going live. You can simulate survey events to see how posts are created and updated.
Credentials are found in the Zid console under API Keys. Store them securely and rotate them periodically. For production apps, use environment variables and secret managers.
Always use least-privilege scopes and secure storage. Regularly review access logs and apply token refresh best practices to protect data.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
