Generate an API key with the surveys.readonly scope, grant access, and keep credentials secure so your requests to endpoints like GET /surveys/ and GET /surveys/submissions can flow through.
In Thankster, create an API connection and paste the Workflows API key to establish a trusted link for data exchange.
GET /surveys/ — list surveys; GET /surveys/submissions — fetch survey submissions; Additional endpoints are available in the API docs and can be used as your needs grow.
Trigger: a new survey submission is created in Workflows API.
Action: send a request to Thankster to generate and send a postcard, then log the result back in Workflows.
GET /surveys/submissions
submission_id, survey_id, recipient_email
Trigger: new or updated survey details are available
Action: fetch survey data, enrich with Thankster template data, then trigger card delivery
GET /surveys/
survey_id, title, status
Trigger: a new submission appears in GET /surveys/submissions
Action: post submission data to Thankster to create or update a card, then record activity in Workflows
GET /surveys/submissions
submission_id, recipient_email, status
Visual workflow building means you can automate end-to-end processes without writing code
Fast setup with ready-made triggers and actions lets you go live quickly
Scalability across campaigns and teams stays simple with centralized configuration
This section defines endpoints, triggers, actions, fields, and the data flow that connects survey data to Thankster card creation.
A specific URL path in the API that exposes a resource or action, such as listing surveys or reading submissions.
An event that starts a workflow, for example a new submission or a status change in a survey.
A callback URL that receives real-time data from an external service when events occur.
Mapping data fields between GHL and Thankster so data lands in the correct templates and records.
Configure a trigger on new submissions to generate and send a personalized Thankster card automatically.
Use endpoint data to tailor card templates per survey category and audience.
Trigger reminder cards via Thankster for respondents who haven’t completed a survey.
In GHL, generate an API key with surveys.readonly scope and note the credential data. In Thankster, add a new API connection and paste the key to establish authorization.
Run a test to verify that GET /surveys/ and GET /surveys/submissions return data, then map fields to templates.
Activate the workflow, monitor results in dashboards, and refine triggers as needed.
No coding is required. Use the visual workflow builder to connect Workflows API to Thankster. You will configure triggers, actions, and data mappings without writing code, guided by templates and samples. If you prefer a code-free approach, rely on pre-built blocks and drag-and-drop connectors to map survey data to card content.
The essential endpoints are GET /surveys/ and GET /surveys/submissions for reading survey data. You may also use additional endpoints provided in the API docs as your use case expands. Browse the docs for examples and field options.
Test the connection by running a quick fetch for surveys and a sample submission. Validate that field mappings render correctly in templates and that Thankster cards are created or scheduled as expected. Check logs and retry if authentication fails.
You typically need the surveys.readonly scope for reading submissions. Depending on actions you perform (e.g., creating cards or updating statuses), you may require additional scopes. Always follow the least-privilege principle and rotate credentials regularly.
Yes. You can trigger multiple cards per submission by duplicating actions or creating multiple branches in the workflow. Use conditional logic to decide which templates to apply. Monitor rate limits and ensure unique identifiers for each card.
Map data fields such as recipient_email, survey_id, and response_text to the corresponding placeholders in your Thankster templates. Use a field-mapping step in the workflow to ensure accurate data transfer.
Refer to the API documentation for endpoint details, example requests, and authentication steps. If you need tailored examples, contact support or consult the developer docs.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
