Create a task for each change
When HasData detects a website change, create a review task in Asana.
Google for Startups AcceleratorHow Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
HasData Explore HasData →
TriggersFires when a scrape, crawl or robot run finishes in HasData.
Fires when HasData returns a new batch of extracted data.
Fires when HasData detects a change on a monitored page.
Extracts the content of a web page with HasData.
Starts a crawl of a whole site in HasData.
Runs a saved scraper, task or robot in HasData.
Asana Explore Asana →
TriggersFires when a new task, job or item is created in Asana.
Fires when a task in Asana is marked complete.
Fires when a task's due date in Asana is coming up.
Fires when a task, job or project changes status in Asana.
Creates a new task, job or item in Asana.
Updates a task's status or assignee in Asana.
Posts a comment on a task in Asana.
Assigns a task in Asana to a team member.
More HasData + Asana workflows
See all HasData + Asana integrations → · Browse the full workflow library →
Enterprise-grade security
Common questions
Can Knit build “Create a task for each change” between HasData and Asana?
Yes — describe it in the box above and Knit's Integrations Agent researches HasData and Asana's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.
Why create tasks from scraped data?
Scraping finds things that need a person to act, like new listings, leads or competitor changes. Creating a task in Asana makes sure someone follows up.
Can I scrape pages attached to a task?
Yes. When a task with a URL is created in Asana, run a scrape in HasData and add the result to the task.