Get more out of awork with Nodest. Pick a ready-made workflow, customise it to fit your needs, and go live in minutes.
When “Time entry updated” fires in awork, Nodest will create or update rows in Google Sheets.
When “Time entry created” fires in awork, Nodest will create or update rows in Google Sheets.
When “Company updated” fires in awork, Nodest will create or update rows in Google Sheets.
When “Company created” fires in awork, Nodest will create or update rows in Google Sheets.
When “Project deleted” fires in awork, Nodest will create or update rows in Google Sheets.
When “Project status changed” fires in awork, Nodest will create or update rows in Google Sheets.
When “Project updated” fires in awork, Nodest will create or update rows in Google Sheets.
When “Project created” fires in awork, Nodest will create or update rows in Google Sheets.
When “Task deleted” fires in awork, Nodest will create or update rows in Google Sheets.
When “Task status changed” fires in awork, Nodest will create or update rows in Google Sheets.
When “Task updated” fires in awork, Nodest will create or update rows in Google Sheets.
When “Task created” fires in awork, Nodest will create or update rows in Google Sheets.
When “Project status changed” fires in awork, Nodest will send a message in Anthropic and create a post in WordPress.
When “Task comment added” fires in awork, Nodest will send a message in Anthropic and create a task in Todoist.
When “Project status changed” fires in awork, Nodest will send a message in Anthropic and send an email in Resend.
When “Task comment added” fires in awork, Nodest will send a message in Anthropic and create a note in Pipedrive.
When “Task comment added” fires in awork, Nodest will send a message in Anthropic and create a task in Google Tasks.
When “Project status changed” fires in awork, Nodest will send a message in Anthropic and send a transactional email in Brevo.
When “Task comment added” fires in awork, Nodest will send a message in Anthropic and create a to-do in Basecamp.
When “Task created” fires in awork, Nodest will send a message in Anthropic and add a comment to a task in awork.
When “Message received” fires in Telegram, Nodest will send a message in Anthropic and create a task in awork.
When “Email replied” fires in ActiveCampaign, Nodest will send a message in Anthropic and create a task in awork.
When “Form submitted” fires in Fluent Forms, Nodest will send a message in Anthropic and create a task in awork.
When “Form submitted” fires in Gravity Forms, Nodest will send a message in Anthropic and create a task in awork.
When “Page created” fires in Notion, Nodest will send a message in Anthropic and create a task in awork.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a task in awork.
When “Bot mentioned” fires in Slack, Nodest will send a message in Anthropic and create a task in awork.
When “Comment posted” fires in WordPress, Nodest will send a message in Anthropic and create a task in awork.
When “Meeting recap created” fires in Calendly, Nodest will send a message in Anthropic and create a task in awork.
When “Conversation closed” fires in Intercom, Nodest will send a message in Anthropic and create a task in awork.
When “Comment added” fires in Todoist, Nodest will send a message in Anthropic and add a comment to a task in awork.
When “Message posted” fires in Basecamp, Nodest will send a message in Anthropic and create a task in awork.
When “Timesheet created” fires in Toggl Track, Nodest will send a message in Anthropic and add a comment to a project in awork.
When “Form submitted” fires in WS Form, Nodest will send a message in Anthropic and create a task in awork.
When “Task comment added” fires in awork, Nodest will send a message in Anthropic and create a record in Airtable.
When “Booking cancelled” fires in Cal.com, Nodest will create a task in awork.
When “Meeting ended” fires in Cal.com, Nodest will create a task in awork.
When “Booking created” fires in Cal.com, Nodest will create a task in awork.
When “Message received” fires in Telegram, Nodest will send a prompt in Gemini and create a task in awork.
When “Message received” fires in Telegram, Nodest will send a prompt in OpenAI and create a task in awork.
When “Message received” fires in Telegram, Nodest will create a task in awork.
When “Task comment added” fires in awork, Nodest will send a message in Telegram.
When “Project status changed” fires in awork, Nodest will send a message in Telegram.
When “Project created” fires in awork, Nodest will send a message in Telegram.
When “Task status changed” fires in awork, Nodest will send a message in Telegram.
When “Task created” fires in awork, Nodest will send a message in Telegram.
When “Company created” fires in awork, Nodest will create a document in Google Docs.
When “Project created” fires in awork, Nodest will create a document in Google Docs.
When “Task comment added” fires in awork, Nodest will send a prompt in Gemini and create a task in Google Tasks.
When “Task comment added” fires in awork, Nodest will send a prompt in OpenAI and create a task in Google Tasks.
When “Task comment added” fires in awork, Nodest will create a task in Google Tasks.
When “Project created” fires in awork, Nodest will create a task in Google Tasks.
When “Task created” fires in awork, Nodest will create a task in Google Tasks.
When “Task created” fires in awork, Nodest will create an event in Google Calendar.
When “Project created” fires in awork, Nodest will create a list in Trello.
When “Task created” fires in awork, Nodest will create a card in Trello.
When “Card created” fires in Trello, Nodest will create a task in awork.
When “Form submitted” fires in WS Form, Nodest will send a prompt in Gemini and create a task in awork.
When “Form submitted” fires in WS Form, Nodest will send a prompt in OpenAI and create a task in awork.
When “Form submitted” fires in WS Form, Nodest will create a task in awork and add tags to a task in awork.
When “Form submitted” fires in WS Form, Nodest will add a comment to a task in awork.
When “Form submitted” fires in WS Form, Nodest will create a company in awork.
When “Form submitted” fires in WS Form, Nodest will create a project in awork.
When “Form submitted” fires in WS Form, Nodest will create a private task in awork.
When “Form submitted” fires in WS Form, Nodest will create a task in awork.
When “Task status changed” fires in awork, Nodest will start a time entry in Toggl Track.
When “Task updated” fires in awork, Nodest will update a task in Toggl Track.
When “Task created” fires in awork, Nodest will create a task in Toggl Track.
When “Company updated” fires in awork, Nodest will update a client in Toggl Track.
When “Company created” fires in awork, Nodest will create a client in Toggl Track.
When “Project deleted” fires in awork, Nodest will delete a project in Toggl Track.
When “Project updated” fires in awork, Nodest will update a project in Toggl Track.
When “Project created” fires in awork, Nodest will create a project in Toggl Track.
When “Time entry deleted” fires in awork, Nodest will delete a time entry in Toggl Track.
When “Time entry updated” fires in awork, Nodest will update a time entry in Toggl Track.
When “Time entry created” fires in awork, Nodest will create a time entry in Toggl Track.
When “Timesheet created” fires in Toggl Track, Nodest will send a prompt in Gemini and add a comment to a project in awork.
When “Timesheet created” fires in Toggl Track, Nodest will send a prompt in OpenAI and add a comment to a project in awork.
When “Member added” fires in Toggl Track, Nodest will invite a user in awork.
When “Timesheet created” fires in Toggl Track, Nodest will add a comment to a project in awork.
When “Task deleted” fires in Toggl Track, Nodest will delete a task in awork.
When “Task updated” fires in Toggl Track, Nodest will update a task in awork.
When “Task created” fires in Toggl Track, Nodest will create a task in awork.
When “Client updated” fires in Toggl Track, Nodest will update a company in awork.
When “Client created” fires in Toggl Track, Nodest will create a company in awork.
When “Project updated” fires in Toggl Track, Nodest will update a project in awork.
When “Project created” fires in Toggl Track, Nodest will create a project in awork.
When “Time entry deleted” fires in Toggl Track, Nodest will delete a time entry in awork.
When “Time entry updated” fires in Toggl Track, Nodest will update a time entry in awork.
When “Time entry created” fires in Toggl Track, Nodest will create a time entry in awork.
When “Message posted” fires in Basecamp, Nodest will send a prompt in Gemini and create a task in awork.
When “Message posted” fires in Basecamp, Nodest will send a prompt in OpenAI and create a task in awork.
When “Schedule entry created” fires in Basecamp, Nodest will create a milestone in awork.
When “Card created” fires in Basecamp, Nodest will create a task in awork.
When “To-do list created” fires in Basecamp, Nodest will create a task list in awork.
When “Message posted” fires in Basecamp, Nodest will add a comment to a project in awork.
When “Comment posted” fires in Basecamp, Nodest will add a comment to a task in awork.
When “To-do assignment changed” fires in Basecamp, Nodest will assign users to a task in awork.
When “To-do completed” fires in Basecamp, Nodest will change a task's status in awork.
When “To-do created” fires in Basecamp, Nodest will add a checklist item to a task in awork.
When “To-do created” fires in Basecamp, Nodest will create a private task in awork.
When “To-do created” fires in Basecamp, Nodest will create a task in awork.
When “Task comment added” fires in awork, Nodest will send a prompt in Gemini and create a to-do in Basecamp.
When “Task comment added” fires in awork, Nodest will send a prompt in OpenAI and create a to-do in Basecamp.
When “Task deleted” fires in awork, Nodest will trash a recording in Basecamp.
When “Project deleted” fires in awork, Nodest will archive a project in Basecamp.
When “Project status changed” fires in awork, Nodest will create a message in Basecamp.
When “Project status changed” fires in awork, Nodest will send a campfire message in Basecamp.
When “Project created” fires in awork, Nodest will create a to-do list in Basecamp.
When “Project created” fires in awork, Nodest will create a project in Basecamp.
When “Task comment added” fires in awork, Nodest will add a comment to a recording in Basecamp.
When “Task updated” fires in awork, Nodest will update a to-do in Basecamp.
When “Task status changed” fires in awork, Nodest will move a card to a column in Basecamp.
When “Task status changed” fires in awork, Nodest will complete a to-do in Basecamp.
When “Task created” fires in awork, Nodest will create a schedule entry in Basecamp.
When “Task created” fires in awork, Nodest will create a card in Basecamp.
When “Task created” fires in awork, Nodest will create a to-do in Basecamp.
When “Comment added” fires in Todoist, Nodest will send a prompt in Gemini and add a comment to a task in awork.
When “Comment added” fires in Todoist, Nodest will send a prompt in OpenAI and add a comment to a task in awork.
When “Project created” fires in Todoist, Nodest will add tags to a project in awork.
When “Project created” fires in Todoist, Nodest will add a member to a project in awork.
When “Project created” fires in Todoist, Nodest will create a milestone in awork.
When “Task updated” fires in Todoist, Nodest will move a task to another project in awork.
When “Task created” fires in Todoist, Nodest will assign users to a task in awork.
When “Task completed” fires in Todoist, Nodest will create a time entry in awork.
When “Task completed” fires in Todoist, Nodest will stop a timer in awork.
When “Task created” fires in Todoist, Nodest will start a timer in awork.
When “Task created” fires in Todoist, Nodest will add a checklist item to a task in awork.
When “Task uncompleted” fires in Todoist, Nodest will remove tags from a task in awork.
When “Task created” fires in Todoist, Nodest will create a task in awork and add tags to a task in awork.
When “Section deleted” fires in Todoist, Nodest will delete a task list in awork.
When “Section updated” fires in Todoist, Nodest will update a task list in awork.
When “Section created” fires in Todoist, Nodest will create a task list in awork.
When “Project deleted” fires in Todoist, Nodest will delete a project in awork.
When “Project archived” fires in Todoist, Nodest will change a project's status in awork.
When “Project updated” fires in Todoist, Nodest will update a project in awork.
When “Project created” fires in Todoist, Nodest will create a project in awork.
When “Comment added” fires in Todoist, Nodest will add a comment to a project in awork.
When “Comment deleted” fires in Todoist, Nodest will delete a task comment in awork.
When “Comment updated” fires in Todoist, Nodest will update a task comment in awork.
When “Comment added” fires in Todoist, Nodest will add a comment to a task in awork.
When “Task deleted” fires in Todoist, Nodest will delete a task in awork.
When “Task completed” fires in Todoist, Nodest will change a task's status in awork.
When “Task updated” fires in Todoist, Nodest will update a task in awork.
When “Task created” fires in Todoist, Nodest will create a private task in awork.
When “Task created” fires in Todoist, Nodest will create a task in awork.
When “Task comment added” fires in awork, Nodest will send a prompt in Gemini and create a task in Todoist.
When “Task comment added” fires in awork, Nodest will send a prompt in OpenAI and create a task in Todoist.
When “Company created” fires in awork, Nodest will create a project in Todoist.
When “Project deleted” fires in awork, Nodest will archive a project in Todoist.
When “Project status changed” fires in awork, Nodest will add a comment to a project in Todoist.
When “Project created” fires in awork, Nodest will create a project in Todoist.
When “Task comment added” fires in awork, Nodest will add a comment to a task in Todoist.
When “Task deleted” fires in awork, Nodest will delete a task in Todoist.
When “Task status changed” fires in awork, Nodest will complete a task in Todoist.
When “Task updated” fires in awork, Nodest will update a task in Todoist.
When “Task created” fires in awork, Nodest will create a task in Todoist.
When “Task comment added” fires in awork, Nodest will send a prompt in Gemini and create a note in Pipedrive.
When “Task comment added” fires in awork, Nodest will send a prompt in OpenAI and create a note in Pipedrive.
When “Company created” fires in awork, Nodest will create an organization in Pipedrive.
When “Task status changed” fires in awork, Nodest will mark an activity as done in Pipedrive.
When “Task created” fires in awork, Nodest will create an activity in Pipedrive.
When “Project created” fires in Pipedrive, Nodest will create a project in awork.
When “Note created” fires in Pipedrive, Nodest will add a comment to a task in awork.
When “Activity created” fires in Pipedrive, Nodest will create a task in awork.
When “Organization updated” fires in Pipedrive, Nodest will update a company in awork.
When “Organization created” fires in Pipedrive, Nodest will create a company in awork.
When “Deal won” fires in Pipedrive, Nodest will create a project in awork.
When “Deal stage changed” fires in Pipedrive, Nodest will change a task's status in awork.
When “Deal created” fires in Pipedrive, Nodest will create a task in awork.
When “Conversation closed” fires in Intercom, Nodest will send a prompt in Gemini and create a task in awork.
When “Conversation closed” fires in Intercom, Nodest will send a prompt in OpenAI and create a task in awork.
When “Company created” fires in awork, Nodest will create or update a company in Intercom.
When “Task comment added” fires in awork, Nodest will reply to a ticket in Intercom.
When “Task status changed” fires in awork, Nodest will update a ticket in Intercom.
When “Task created” fires in awork, Nodest will create a ticket in Intercom.
When “Lead converted to user” fires in Intercom, Nodest will create a task in awork.
When “Company updated” fires in Intercom, Nodest will update a company in awork.
When “Company created” fires in Intercom, Nodest will create a company in awork.
When “Conversation rated” fires in Intercom, Nodest will create a task in awork.
When “Conversation priority updated” fires in Intercom, Nodest will create a task in awork.
When “Ticket note added” fires in Intercom, Nodest will add a comment to a task in awork.
When “Ticket state updated” fires in Intercom, Nodest will change a task's status in awork.
When “Ticket created” fires in Intercom, Nodest will create a task in awork.
When “Meeting recap created” fires in Calendly, Nodest will send a prompt in Gemini and create a task in awork.
When “Meeting recap created” fires in Calendly, Nodest will send a prompt in OpenAI and create a task in awork.
When “Routing form submitted” fires in Calendly, Nodest will create a task in awork.
When “Invitee marked as no-show” fires in Calendly, Nodest will create a task in awork.
When “Invitee created” fires in Calendly, Nodest will create a task in awork.
When “Task comment added” fires in awork, Nodest will send a prompt in Gemini and create a record in Airtable.
When “Task comment added” fires in awork, Nodest will send a prompt in OpenAI and create a record in Airtable.
When “Time entry deleted” fires in awork, Nodest will delete a record in Airtable.
When “Time entry updated” fires in awork, Nodest will create or update a record in Airtable.
When “Time entry created” fires in awork, Nodest will create a record in Airtable.
When “Company updated” fires in awork, Nodest will create or update a record in Airtable.
When “Company created” fires in awork, Nodest will create or update a record in Airtable.
When “Project deleted” fires in awork, Nodest will delete a record in Airtable.
When “Project status changed” fires in awork, Nodest will create or update a record in Airtable.
When “Project updated” fires in awork, Nodest will create or update a record in Airtable.
When “Project created” fires in awork, Nodest will create a record in Airtable.
When “Task comment added” fires in awork, Nodest will add a comment to a record in Airtable.
When “Task deleted” fires in awork, Nodest will delete a record in Airtable.
When “Task status changed” fires in awork, Nodest will create or update a record in Airtable.
When “Task updated” fires in awork, Nodest will create or update a record in Airtable.
When “Task created” fires in awork, Nodest will create a record in Airtable.
When “Project status changed” fires in awork, Nodest will send a prompt in Gemini and create a post in WordPress.
When “Project status changed” fires in awork, Nodest will send a prompt in OpenAI and create a post in WordPress.
When “Post published” fires in WordPress, Nodest will create a task in awork.
When “Comment posted” fires in WordPress, Nodest will send a prompt in Gemini and create a task in awork.
When “Comment posted” fires in WordPress, Nodest will send a prompt in OpenAI and create a task in awork.
When “Comment posted” fires in WordPress, Nodest will create a task in awork.
When “Project status changed” fires in awork, Nodest will update an order in WooCommerce.
When “Task status changed” fires in awork, Nodest will create an order note in WooCommerce.
When “Order status changed” fires in WooCommerce, Nodest will change a task's status in awork.
When “Order placed” fires in WooCommerce, Nodest will create a project in awork.
When “Order placed” fires in WooCommerce, Nodest will create a task in awork.
When “Task comment added” fires in awork, Nodest will send a direct message in Slack.
When “Task created” fires in awork, Nodest will send a direct message in Slack.
When “Task status changed” fires in awork, Nodest will send a channel message in Slack.
When “Project status changed” fires in awork, Nodest will send a channel message in Slack.
When “Project created” fires in awork, Nodest will send a channel message in Slack.
When “Bot received a direct message” fires in Slack, Nodest will create a private task in awork.
When “Bot mentioned” fires in Slack, Nodest will send a prompt in Gemini and create a task in awork.
When “Bot mentioned” fires in Slack, Nodest will send a prompt in OpenAI and create a task in awork.
When “Bot mentioned” fires in Slack, Nodest will create a task in awork.
When “Project status changed” fires in awork, Nodest will send a prompt in Gemini and send an email in Resend.
When “Project status changed” fires in awork, Nodest will send a prompt in OpenAI and send an email in Resend.
When “Project status changed” fires in awork, Nodest will send an email from a template in Resend.
When “Email failed” fires in Resend, Nodest will create a task in awork.
When “Email received” fires in Resend, Nodest will send a prompt in Gemini and create a task in awork.
When “Email received” fires in Resend, Nodest will send a prompt in OpenAI and create a task in awork.
When “Email received” fires in Resend, Nodest will create a task in awork.
When “Task comment added” fires in awork, Nodest will add a comment in Notion.
When “Company created” fires in awork, Nodest will create a page in a database in Notion.
When “Project status changed” fires in awork, Nodest will update a page in Notion.
When “Project created” fires in awork, Nodest will create a page in a database in Notion.
When “Task status changed” fires in awork, Nodest will update a page in Notion.
When “Task created” fires in awork, Nodest will create a page in a database in Notion.
When “Property changed” fires in Notion, Nodest will change a task's status in awork.
When “Page created” fires in Notion, Nodest will send a prompt in Gemini and create a task in awork.
When “Page created” fires in Notion, Nodest will send a prompt in OpenAI and create a task in awork.
When “Page created” fires in Notion, Nodest will create a task in awork.
When “Project created” fires in awork, Nodest will create a board in Monday.com.
When “Task comment added” fires in awork, Nodest will add an update in Monday.com.
When “Task status changed” fires in awork, Nodest will update an item in Monday.com.
When “Task created” fires in awork, Nodest will create an item in Monday.com.
When “Item name changed” fires in Monday.com, Nodest will update a task in awork.
When “Update posted” fires in Monday.com, Nodest will add a comment to a task in awork.
When “Status changed” fires in Monday.com, Nodest will change a task's status in awork.
When “Item created” fires in Monday.com, Nodest will create a task in awork.
When “Payment refunded” fires in MemberPress, Nodest will create a task in awork.
When “Subscription stopped” fires in MemberPress, Nodest will create a task in awork.
When “Payment failed” fires in MemberPress, Nodest will create a task in awork.
When “Member signed up” fires in MemberPress, Nodest will create a task in awork.
When “Campaign sent” fires in Mailchimp, Nodest will create a task in awork.
When “Project status changed” fires in awork, Nodest will post a project update in Linear.
When “Project created” fires in awork, Nodest will create a project in Linear.
When “Task comment added” fires in awork, Nodest will add a comment in Linear.
When “Task status changed” fires in awork, Nodest will update an issue in Linear.
When “Task updated” fires in awork, Nodest will update an issue in Linear.
When “Task created” fires in awork, Nodest will create an issue in Linear.
When “Project update posted” fires in Linear, Nodest will add a comment to a project in awork.
When “Project created” fires in Linear, Nodest will create a project in awork.
When “Comment created” fires in Linear, Nodest will add a comment to a task in awork.
When “Issue updated” fires in Linear, Nodest will update a task in awork.
When “Issue created” fires in Linear, Nodest will create a task in awork.
When “Form submitted” fires in Gravity Forms, Nodest will create a company in awork.
When “Form submitted” fires in Gravity Forms, Nodest will create a project in awork.
When “Form submitted” fires in Gravity Forms, Nodest will send a prompt in Gemini and create a task in awork.
When “Form submitted” fires in Gravity Forms, Nodest will send a prompt in OpenAI and create a task in awork.
When “Form submitted” fires in Gravity Forms, Nodest will create a task in awork.
When “Company created” fires in awork, Nodest will create a row in Google Sheets.
When “Project status changed” fires in awork, Nodest will update matching rows in Google Sheets.
When “Project created” fires in awork, Nodest will create a row in Google Sheets.
When “Task status changed” fires in awork, Nodest will update matching rows in Google Sheets.
When “Task created” fires in awork, Nodest will create a row in Google Sheets.
When “Time entry deleted” fires in awork, Nodest will update matching rows in Google Sheets.
When “Time entry updated” fires in awork, Nodest will update matching rows in Google Sheets.
When “Time entry created” fires in awork, Nodest will create a row in Google Sheets.
When “Task status changed” fires in awork, Nodest will update entry status in Fluent Forms.
When “Task status changed” fires in awork, Nodest will add a note to an entry in Fluent Forms.
When “Form submitted” fires in Fluent Forms, Nodest will create a company in awork.
When “Form submitted” fires in Fluent Forms, Nodest will create a project in awork.
When “Form submitted” fires in Fluent Forms, Nodest will send a prompt in Gemini and create a task in awork.
When “Form submitted” fires in Fluent Forms, Nodest will send a prompt in OpenAI and create a task in awork.
When “Form submitted” fires in Fluent Forms, Nodest will create a task in awork.
When “Download published” fires in Easy Digital Downloads, Nodest will create a task in awork.
When “Purchase completed” fires in Easy Digital Downloads, Nodest will create a task in awork.
When “Project created” fires in awork, Nodest will translate text in DeepL and add a comment to a project in awork.
When “Task created” fires in awork, Nodest will translate text in DeepL and add a comment to a task in awork.
When “Task comment added” fires in awork, Nodest will create a comment on a task in ClickUp.
When “Task status changed” fires in awork, Nodest will update a task in ClickUp.
When “Task updated” fires in awork, Nodest will update a task in ClickUp.
When “Task created” fires in awork, Nodest will create a task in ClickUp.
When “Comment posted on a task” fires in ClickUp, Nodest will add a comment to a task in awork.
When “Task status changed” fires in ClickUp, Nodest will change a task's status in awork.
When “Task updated” fires in ClickUp, Nodest will update a task in awork.
When “Task created” fires in ClickUp, Nodest will create a task in awork.
When “Project status changed” fires in awork, Nodest will send a prompt in Gemini and send a transactional email in Brevo.
When “Project status changed” fires in awork, Nodest will send a prompt in OpenAI and send a transactional email in Brevo.
When “Project status changed” fires in awork, Nodest will create a note in Brevo.
When “Project status changed” fires in awork, Nodest will update a deal in Brevo.
When “Project created” fires in awork, Nodest will create a deal in Brevo.
When “Company updated” fires in awork, Nodest will update a company in Brevo.
When “Company created” fires in awork, Nodest will create a company in Brevo.
When “Contact added to list” fires in Brevo, Nodest will create a task in awork.
When “Transactional email hard bounced” fires in Brevo, Nodest will create a task in awork.
When “Project created” fires in awork, Nodest will create a project in Asana.
When “Task comment added” fires in awork, Nodest will add a comment in Asana.
When “Task status changed” fires in awork, Nodest will complete a task in Asana.
When “Task updated” fires in awork, Nodest will update a task in Asana.
When “Task created” fires in awork, Nodest will create a task in Asana.
When “Comment added” fires in Asana, Nodest will add a comment to a task in awork.
When “Task completed” fires in Asana, Nodest will change a task's status in awork.
When “Task updated” fires in Asana, Nodest will update a task in awork.
When “Task created” fires in Asana, Nodest will create a task in awork.
When “Task status changed” fires in awork, Nodest will update a task in ActiveCampaign.
When “Project status changed” fires in awork, Nodest will update a deal in ActiveCampaign.
When “Project status changed” fires in awork, Nodest will add a note to a deal in ActiveCampaign.
When “Company updated” fires in awork, Nodest will update an account in ActiveCampaign.
When “Company created” fires in awork, Nodest will create an account in ActiveCampaign.
When “SMS reply received” fires in ActiveCampaign, Nodest will create a task in awork.
When “Email replied” fires in ActiveCampaign, Nodest will send a prompt in Gemini and create a task in awork.
When “Email replied” fires in ActiveCampaign, Nodest will send a prompt in OpenAI and create a task in awork.
When “Email replied” fires in ActiveCampaign, Nodest will create a task in awork.
When “Deal note added” fires in ActiveCampaign, Nodest will add a comment to a project in awork.
When “Deal task created” fires in ActiveCampaign, Nodest will create a task in awork.
When “Deal updated” fires in ActiveCampaign, Nodest will change a project's status in awork.
When “Deal created” fires in ActiveCampaign, Nodest will create a project in awork.
Sign up for free and start building in minutes.
