Turn training feedback into clear actions fast. New or updated rows in Airtable are checked, low scores trigger tasks and alerts, and high scores can be shared on LinkedIn. L and D and HR teams get quicker follow up and better visibility.

The flow starts with an Airtable Trigger that polls the Created field every minute. A Switch checks the rating and opens the right Usertask through HTTP requests, each with a callback URL to an n8n webhook. When Usertask sends results back to the webhook, a second Switch directs next steps. Emails notify owners for poor or mixed scores, a task detail call enriches the message, and the LinkedIn node posts recognition for very good scores under the company profile.

Setup needs an Airtable base for feedback, a Usertask API key and client ID, LinkedIn company access, and an SMTP sender. Expect faster handling of poor scores, less manual sorting, and public praise for strong results. Use it for employee training, onboarding classes, and partner workshops. Adjust the Switch conditions to match your rating scale and update the callback URL to your n8n webhook.

• Airtable Trigger watches the Created field and polls every minute for new or updated feedback.
• Rating based Switch routes items into dissatisfaction, fair to good, or very good paths.
• HTTP Request nodes create Usertask instances with API key and client ID headers and a webhook callback URL.
• Webhook receives Usertask results so the flow can continue without manual checks.
• Task detail fetch enriches emails with the exact action and context owners need.
• Email nodes send alerts for poor scores and marketing info after webhook responses.
• LinkedIn node posts recognition from the organization profile for top ratings using a templated message.
• Second Switch after the webhook directs final actions based on the returned result.

• Reduce manual triage from 1 hour to 5 minutes per feedback batch
• Streamline feedback routing by up to 80 percent with clear branches
• Improve response time to low scores from days to same day
• Connect Airtable, Usertask, LinkedIn, and email in one flow
• Increase data consistency by standardizing tasks and messages

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Airtable, Usertask, LinkedIn and SMTP. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create an Airtable OAuth2 credential. Double click the Airtable Trigger node, choose the credential, and authorize your Airtable account.
4. In the Airtable Trigger node, select your base and table. Set the trigger field to Created and keep the poll time as every minute or adjust to your needs. Save and test by adding a new row.
5. For Usertask, get your API key and client ID from the Usertask admin or API page. In each HTTP Request node that calls Usertask, click Create new credential or add the headers X-API-KEY and X-CLIENT-ID using secure credentials.
6. Open the Webhook node and copy its production URL. In every Usertask create task body, update callbackUrl to match that webhook URL so Usertask can send results back to n8n.
7. Create a LinkedIn OAuth2 credential in n8n. Open the LinkedIn node, pick post as organization, select the company profile, and keep or edit the message template.
8. Set up your SMTP sender in n8n. In each Email node, choose the SMTP credential, set the From and To fields, and personalize the subject and body placeholders.
9. Adjust the Switch conditions to match your rating scale in Airtable. For example, send 1 to 2 stars to the dissatisfaction path, 3 to 4 stars to follow up, and 5 stars to recognition.
10. Run a full test: add a poor rating row in Airtable. Confirm a Usertask is created, the webhook receives a callback, and the alert email arrives.
11. Run a positive rating test: add a very good score. Confirm the LinkedIn post is created and the marketing email is sent.
12. If the Airtable Trigger does not fire, check the base and table IDs, the Created field mapping, and the poll interval. Verify the credential is authorized.
13. If the webhook does not receive a callback, confirm the callbackUrl is reachable over HTTPS, the path matches the Webhook node, and the Usertask headers are valid.