Pipedrive + any website
Read a table, a price or a listing on the page you're on and send it to Pipedrive.
Use Pipedrive in workflows that start from the page you're on — straight from your browser to Pipedrive, nothing in between.
Each action is a node you drop on the canvas. Pair it with any of the 10 triggers — a schedule, a right-click, a page change.
Example actions · Full list in the docs
Read a table, a price or a listing on the page you're on and send it to Pipedrive.
Classify, summarise or rewrite with a model that runs in your browser before it reaches Pipedrive.
No published templates use Pipedrive yet. Docs recipe ↗
Generate an access token or API key in your Pipedrive settings. Give it only the access your workflows need.
Add a Pipedrive credential in AWFlow and paste the token. Save it locally in this browser, or to your account when signed in.
Pick the credential in a Pipedrive node and press Run in the editor. If the step succeeds, the credential works.
No. When a step runs, your browser sends the request to Pipedrive. AWFlow's servers never relay the call.
No. Local mode works without an account and keeps the Pipedrive credential in this browser. Signed in, you choose per credential: this browser or your account. Installing a template from the Marketplace needs sign-in.
No. Workflows run while your browser is open. A Wait of a minute or more in the extension survives closing the tab and picks up where it left off, for up to 30 days.
No. Workflows run in your browser, so there are no per-task fees. Pipedrive applies its own usual limits.