To turn Skool member requests into Asana tasks, create one Asana project for community requests, define which posts, comments and DMs count as a request, and send each one into the project with the member's name, a link to the original post, an owner and a due date. The goal is simple: no member request depends on someone remembering it.
What counts as a request
Members ask for things all day. Not all of them need a task. These usually do:
• Access problems: "I can't see the course," "my login isn't working"
• Content requests: "Could you do a lesson on..."
• Questions that need research or a longer answer than a comment
• Support or billing issues that need a team member
• Testimonials you want to ask permission to use
Simple questions answered in the thread don't need a task. Answer them and move on.
Step 1: Set up the Asana project
Create a project called "Community requests" with sections:
• New
• In progress
• Waiting on member
• Done
Add a few custom fields: request type (access, content, support, testimonial), member name, and a link to the Skool post or comment. The link matters most. Without it, whoever picks up the task has to hunt for context.
Step 2: Decide how requests get in
Pick one of these and stick with it:
• Manual: whoever reads the feed creates the task. Works for small communities if you review the feed at set times.
• Keyword-based: an automation watches posts and comments for words like "access," "login," "refund" or "can you make," and creates a task through a webhook into Make, n8n or another automation tool connected to Asana.
• DM-based: anyone who answers a DM that needs follow-up creates the task before closing the conversation.
Step 3: Write the task the same way every time
Title: "[Type] [Member name]: [short summary]"
Example: "Access: Jordan P: can't open Module 2"
Description: the link, the member's exact words, and what they need. Assign an owner and a due date before saving. A task without an owner is just a note.
Step 4: Set response times
Agree on targets, for example:
• Access and billing: same day
• Support questions: within 24 hours
• Content requests: acknowledge within 48 hours, build when it fits the plan
Step 5: Close the loop with the member
When a task moves to Done, reply in the original thread or DM: "Fixed, you should see Module 2 now." Members remember being heard far more than they remember how fast you were.
Mistakes to avoid
• Creating a task for every comment. Your project fills with noise and people stop checking it.
• Tasks without a link to the original post
• Content requests that sit in New forever. Review them monthly and tell members which ones you're building.
• Fixing the problem but never telling the member
A worked example
Say a community of 600 members gets 10 to 15 real requests a week. Before Asana, two access issues a month slipped through and turned into angry posts. With one project, keyword alerts for "access" and "login," and a same-day target for access tasks, those issues get fixed the day they appear. The monthly content request review also gives you your next three lessons.
StickyHive workflows can trigger on a keyword in a post or comment and send a webhook, so a request in the feed can become an Asana task through your automation tool. The Skool automation tools page shows the triggers and integrations. What kind of member request most often slips through the cracks in your community?