Get more out of Google Sheets with Nodest. Pick a ready-made workflow, customise it to fit your needs, and go live in minutes.
When “Form submitted” fires in WS Form, Nodest will send a prompt in Gemini and create or update rows in Google Sheets.
When “Form submitted” fires in WS Form, Nodest will send a prompt in OpenAI and create or update rows in Google Sheets.
When “Form submitted” fires in WS Form, Nodest will create or update rows in Google Sheets.
When “Comment posted” fires in WordPress, Nodest will create or update rows in Google Sheets.
When “Page published” fires in WordPress, Nodest will create or update rows in Google Sheets.
When “Post published” fires in WordPress, Nodest will create or update rows in Google Sheets.
When “User registered” fires in WordPress, Nodest will create or update rows in Google Sheets.
When “Customer created” fires in WooCommerce, Nodest will create or update rows in Google Sheets.
When “Payment complete” fires in WooCommerce, Nodest will create or update rows in Google Sheets.
When “Order status changed” fires in WooCommerce, Nodest will create or update rows in Google Sheets.
When “Order placed” fires in WooCommerce, Nodest will create or update rows in Google Sheets.
When “Comment added to a card” fires in Trello, Nodest will create or update rows in Google Sheets.
When “Label added to a card” fires in Trello, Nodest will create or update rows in Google Sheets.
When “Member added to a card” fires in Trello, Nodest will create or update rows in Google Sheets.
When “Card deleted” fires in Trello, Nodest will create or update rows in Google Sheets.
When “Card archived” fires in Trello, Nodest will create or update rows in Google Sheets.
When “Card due date changed” fires in Trello, Nodest will create or update rows in Google Sheets.
When “Card moved to a list” fires in Trello, Nodest will create or update rows in Google Sheets.
When “Card updated” fires in Trello, Nodest will create or update rows in Google Sheets.
When “Card created” fires in Trello, Nodest will create or update rows in Google Sheets.
When “Timesheet updated” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Timesheet created” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Member updated” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Member added” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Task updated” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Task created” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Client updated” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Client created” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Project updated” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Project created” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Time entry deleted” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Time entry updated” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Time entry created” fires in Toggl Track, Nodest will create or update rows in Google Sheets.
When “Project archived” fires in Todoist, Nodest will create or update rows in Google Sheets.
When “Project updated” fires in Todoist, Nodest will create or update rows in Google Sheets.
When “Project created” fires in Todoist, Nodest will create or update rows in Google Sheets.
When “Task deleted” fires in Todoist, Nodest will create or update rows in Google Sheets.
When “Task uncompleted” fires in Todoist, Nodest will create or update rows in Google Sheets.
When “Task completed” fires in Todoist, Nodest will create or update rows in Google Sheets.
When “Task updated” fires in Todoist, Nodest will create or update rows in Google Sheets.
When “Task created” fires in Todoist, Nodest will create or update rows in Google Sheets.
When “Callback query received” fires in Telegram, Nodest will create or update rows in Google Sheets.
When “Message received” fires in Telegram, Nodest will create or update rows in Google Sheets.
When “Channel deleted” fires in Slack, Nodest will create or update rows in Google Sheets.
When “Channel archived” fires in Slack, Nodest will create or update rows in Google Sheets.
When “Channel renamed” fires in Slack, Nodest will create or update rows in Google Sheets.
When “Channel created” fires in Slack, Nodest will create or update rows in Google Sheets.
When “Member joined workspace” fires in Slack, Nodest will create or update rows in Google Sheets.
When “Email failed” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Email marked as spam” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Email bounced” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Email clicked” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Email opened” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Email delivered” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Suppression added” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Contact deleted” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Contact updated” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Contact created” fires in Resend, Nodest will create or update rows in Google Sheets.
When “Product updated” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Product created” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Project task completed” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Project task created” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Project updated” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Project created” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Activity completed” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Activity created” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Lead updated” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Lead created” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Organization updated” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Organization created” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Person deleted” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Person updated” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Person created” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Deal deleted” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Deal lost” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Deal won” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Deal stage changed” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Deal updated” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Deal created” fires in Pipedrive, Nodest will create or update rows in Google Sheets.
When “Page restored” fires in Notion, Nodest will create or update rows in Google Sheets.
When “Page trashed” fires in Notion, Nodest will create or update rows in Google Sheets.
When “Page moved into database” fires in Notion, Nodest will create or update rows in Google Sheets.
When “Page content updated” fires in Notion, Nodest will create or update rows in Google Sheets.
When “Property changed” fires in Notion, Nodest will create or update rows in Google Sheets.
When “Page created” fires in Notion, Nodest will create or update rows in Google Sheets.
When “Subitem created” fires in Monday.com, Nodest will create or update rows in Google Sheets.
When “Item deleted” fires in Monday.com, Nodest will create or update rows in Google Sheets.
When “Item archived” fires in Monday.com, Nodest will create or update rows in Google Sheets.
When “Item moved to group” fires in Monday.com, Nodest will create or update rows in Google Sheets.
When “Column value changed” fires in Monday.com, Nodest will create or update rows in Google Sheets.
When “Status changed” fires in Monday.com, Nodest will create or update rows in Google Sheets.
When “Item name changed” fires in Monday.com, Nodest will create or update rows in Google Sheets.
When “Item created” fires in Monday.com, Nodest will create or update rows in Google Sheets.
When “Payment refunded” fires in MemberPress, Nodest will create or update rows in Google Sheets.
When “Payment failed” fires in MemberPress, Nodest will create or update rows in Google Sheets.
When “Payment completed” fires in MemberPress, Nodest will create or update rows in Google Sheets.
When “Subscription stopped” fires in MemberPress, Nodest will create or update rows in Google Sheets.
When “Subscription resumed” fires in MemberPress, Nodest will create or update rows in Google Sheets.
When “Subscription paused” fires in MemberPress, Nodest will create or update rows in Google Sheets.
When “Subscription created” fires in MemberPress, Nodest will create or update rows in Google Sheets.
When “Member signed up” fires in MemberPress, Nodest will create or update rows in Google Sheets.
When “Member added” fires in MemberPress, Nodest will create or update rows in Google Sheets.
When “Campaign sent” fires in Mailchimp, Nodest will create or update rows in Google Sheets.
When “Member email changed” fires in Mailchimp, Nodest will create or update rows in Google Sheets.
When “Member cleaned” fires in Mailchimp, Nodest will create or update rows in Google Sheets.
When “Member profile updated” fires in Mailchimp, Nodest will create or update rows in Google Sheets.
When “Member unsubscribed” fires in Mailchimp, Nodest will create or update rows in Google Sheets.
When “Member subscribed” fires in Mailchimp, Nodest will create or update rows in Google Sheets.
When “Document updated” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Document created” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Cycle updated” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Cycle created” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Project update posted” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Project removed” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Project updated” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Project created” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Issue removed” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Issue updated” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Issue created” fires in Linear, Nodest will create or update rows in Google Sheets.
When “Article unpublished” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Article updated” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Article published” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Ticket rated” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Ticket closed” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Ticket resolved” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Ticket state updated” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Ticket created” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Conversation rated” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Conversation closed” fires in Intercom, Nodest will send a prompt in Gemini and create or update rows in Google Sheets.
When “Conversation closed” fires in Intercom, Nodest will send a prompt in OpenAI and create or update rows in Google Sheets.
When “Conversation closed” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Conversation priority updated” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Conversation assigned” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Conversation created” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Company updated” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Company created” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Contact archived” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Contact unsubscribed” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Contact subscribed” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Visitor signed up” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Lead converted to user” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Lead updated” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Lead created” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “User updated” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “User created” fires in Intercom, Nodest will create or update rows in Google Sheets.
When “Form submitted” fires in Gravity Forms, Nodest will send a prompt in Gemini and create or update rows in Google Sheets.
When “Form submitted” fires in Gravity Forms, Nodest will send a prompt in OpenAI and create or update rows in Google Sheets.
When “Form submitted” fires in Gravity Forms, Nodest will create or update rows in Google Sheets.
When “Entry deleted” fires in Fluent Forms, Nodest will create or update rows in Google Sheets.
When “Partial submission saved” fires in Fluent Forms, Nodest will create or update rows in Google Sheets.
When “Note added to entry” fires in Fluent Forms, Nodest will create or update rows in Google Sheets.
When “Payment refunded” fires in Fluent Forms, Nodest will create or update rows in Google Sheets.
When “Subscription cancelled” fires in Fluent Forms, Nodest will create or update rows in Google Sheets.
When “Subscription payment received” fires in Fluent Forms, Nodest will create or update rows in Google Sheets.
When “Payment status changed” fires in Fluent Forms, Nodest will create or update rows in Google Sheets.
When “Entry status changed” fires in Fluent Forms, Nodest will create or update rows in Google Sheets.
When “Form submitted” fires in Fluent Forms, Nodest will send a prompt in Gemini and create or update rows in Google Sheets.
When “Form submitted” fires in Fluent Forms, Nodest will send a prompt in OpenAI and create or update rows in Google Sheets.
When “Form submitted” fires in Fluent Forms, Nodest will create or update rows in Google Sheets.
When “File downloaded” fires in Easy Digital Downloads, Nodest will create or update rows in Google Sheets.
When “Download published” fires in Easy Digital Downloads, Nodest will create or update rows in Google Sheets.
When “Purchase completed” fires in Easy Digital Downloads, Nodest will create or update rows in Google Sheets.
When “Customer created” fires in Easy Digital Downloads, Nodest will create or update rows in Google Sheets.
When “Comment posted on a task” fires in ClickUp, Nodest will create or update rows in Google Sheets.
When “Task deleted” fires in ClickUp, Nodest will create or update rows in Google Sheets.
When “Task tag changed” fires in ClickUp, Nodest will create or update rows in Google Sheets.
When “Task moved” fires in ClickUp, Nodest will create or update rows in Google Sheets.
When “Task due date changed” fires in ClickUp, Nodest will create or update rows in Google Sheets.
When “Task assignee changed” fires in ClickUp, Nodest will create or update rows in Google Sheets.
When “Task status changed” fires in ClickUp, Nodest will create or update rows in Google Sheets.
When “Task updated” fires in ClickUp, Nodest will create or update rows in Google Sheets.
When “Task created” fires in ClickUp, Nodest will create or update rows in Google Sheets.
When “Event type updated” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Event type created” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Meeting recap updated” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Meeting recap created” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Routing form submitted” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Contact updated” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Contact created” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Invitee no-show removed” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Invitee marked as no-show” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Invitee canceled” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Invitee created” fires in Calendly, Nodest will create or update rows in Google Sheets.
When “Team booking cancelled” fires in Cal.com, Nodest will create or update rows in Google Sheets.
When “Team booking rescheduled” fires in Cal.com, Nodest will create or update rows in Google Sheets.
When “Team booking created” fires in Cal.com, Nodest will create or update rows in Google Sheets.
When “Meeting ended” fires in Cal.com, Nodest will create or update rows in Google Sheets.
When “Booking paid” fires in Cal.com, Nodest will create or update rows in Google Sheets.
When “Booking requested” fires in Cal.com, Nodest will create or update rows in Google Sheets.
When “Booking cancelled” fires in Cal.com, Nodest will create or update rows in Google Sheets.
When “Booking rescheduled” fires in Cal.com, Nodest will create or update rows in Google Sheets.
When “Booking created” fires in Cal.com, Nodest will create or update rows in Google Sheets.
When “Marketing email clicked” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Transactional email blocked” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Transactional email marked as spam” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Marketing email marked as spam” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Transactional email hard bounced” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Marketing email hard bounced” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Contact deleted” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Contact unsubscribed” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Contact added to list” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Contact updated” fires in Brevo, Nodest will create or update rows in Google Sheets.
When “Schedule entry created” fires in Basecamp, Nodest will create or update rows in Google Sheets.
When “Card created” fires in Basecamp, Nodest will create or update rows in Google Sheets.
When “To-do assignment changed” fires in Basecamp, Nodest will create or update rows in Google Sheets.
When “To-do completed” fires in Basecamp, Nodest will create or update rows in Google Sheets.
When “To-do created” fires in Basecamp, Nodest will create or update rows in Google Sheets.
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 “Task deleted” fires in Asana, Nodest will create or update rows in Google Sheets.
When “Comment added” fires in Asana, Nodest will create or update rows in Google Sheets.
When “Task completed” fires in Asana, Nodest will create or update rows in Google Sheets.
When “Task updated” fires in Asana, Nodest will create or update rows in Google Sheets.
When “Task created” fires in Asana, Nodest will create or update rows in Google Sheets.
When “SMS reply received” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Email replied” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Link clicked” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Deal updated” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Deal created” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Email bounced” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Contact unsubscribed from SMS” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Contact unsubscribed from list” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Contact subscribed to list” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Contact updated” fires in ActiveCampaign, Nodest will create or update rows in Google Sheets.
When “Form submitted” fires in Fluent Forms, Nodest will send a message in Anthropic and create a row in Google Sheets.
When “Form submitted” fires in Gravity Forms, Nodest will send a message in Anthropic and create a row in Google Sheets.
When “Comment posted” fires in WordPress, Nodest will send a message in Anthropic and create a row in Google Sheets.
When “Conversation closed” fires in Intercom, Nodest will send a message in Anthropic and create a row in Google Sheets.
When “Comment added” fires in Todoist, Nodest will send a message in Anthropic and create a row in Google Sheets.
When “Message posted” fires in Basecamp, Nodest will send a message in Anthropic and create a row in Google Sheets.
When “Form submitted” fires in WS Form, Nodest will send a message in Anthropic and create a row in Google Sheets.
When “Booking requested” fires in Cal.com, Nodest will create a row in Google Sheets.
When “Meeting ended” fires in Cal.com, Nodest will create a row in Google Sheets.
When “Booking paid” fires in Cal.com, Nodest will create a row in Google Sheets.
When “Booking rescheduled” fires in Cal.com, Nodest will create a row in Google Sheets.
When “Booking cancelled” fires in Cal.com, Nodest will create a row in Google Sheets.
When “Booking created” fires in Cal.com, Nodest will create a row in Google Sheets.
When “Callback query received” fires in Telegram, Nodest will create a row in Google Sheets.
When “Channel post received” fires in Telegram, Nodest will create a row in Google Sheets.
When “Message received” fires in Telegram, Nodest will create a row in Google Sheets.
When “Member added to a card” fires in Trello, Nodest will create a row in Google Sheets.
When “Checklist item completed” fires in Trello, Nodest will create a row in Google Sheets.
When “Comment added to a card” fires in Trello, Nodest will create a row in Google Sheets.
When “Card archived” fires in Trello, Nodest will create a row in Google Sheets.
When “Card moved to a list” fires in Trello, Nodest will create a row in Google Sheets.
When “Card created” fires in Trello, Nodest will create a row in Google Sheets.
When “Form submitted” fires in WS Form, Nodest will send a prompt in Gemini and create a row in Google Sheets.
When “Form submitted” fires in WS Form, Nodest will send a prompt in OpenAI and create a row in Google Sheets.
When “Form submitted” fires in WS Form, Nodest will update matching rows in Google Sheets.
When “Form submitted” fires in WS Form, Nodest will create a row in Google Sheets.
When “Form submitted” fires in WS Form, Nodest will translate text in DeepL and create a row in Google Sheets.
When “Client created” fires in Toggl Track, Nodest will create a spreadsheet in Google Sheets.
When “Project created” fires in Toggl Track, Nodest will add a sheet to a spreadsheet in Google Sheets.
When “Member removed” fires in Toggl Track, Nodest will create a row in Google Sheets.
When “Member added” fires in Toggl Track, Nodest will create a row in Google Sheets.
When “Task created” fires in Toggl Track, Nodest will create a row in Google Sheets.
When “Client created” fires in Toggl Track, Nodest will create a row in Google Sheets.
When “Project updated” fires in Toggl Track, Nodest will update matching rows in Google Sheets.
When “Project created” fires in Toggl Track, Nodest will create a row in Google Sheets.
When “Timesheet updated” fires in Toggl Track, Nodest will update matching rows in Google Sheets.
When “Timesheet created” fires in Toggl Track, Nodest will create a row in Google Sheets.
When “Time entry deleted” fires in Toggl Track, Nodest will delete a row in Google Sheets.
When “Time entry updated” fires in Toggl Track, Nodest will update matching rows in Google Sheets.
When “Time entry created” fires in Toggl Track, Nodest will create a row in Google Sheets.
When “Message posted” fires in Basecamp, Nodest will send a prompt in Gemini and create a row in Google Sheets.
When “Message posted” fires in Basecamp, Nodest will send a prompt in OpenAI and create a row in Google Sheets.
When “To-do list created” fires in Basecamp, Nodest will add a sheet to a spreadsheet in Google Sheets.
When “To-do list created” fires in Basecamp, Nodest will create a spreadsheet in Google Sheets.
When “To-do list created” fires in Basecamp, Nodest will create a row in Google Sheets.
When “Schedule entry created” fires in Basecamp, Nodest will create a row in Google Sheets.
When “Document created” fires in Basecamp, Nodest will create a row in Google Sheets.
When “Message posted” fires in Basecamp, Nodest will create a row in Google Sheets.
When “Comment posted” fires in Basecamp, Nodest will create a row in Google Sheets.
When “Card created” fires in Basecamp, Nodest will create a row in Google Sheets.
When “To-do assignment changed” fires in Basecamp, Nodest will update a row in Google Sheets.
When “To-do assignment changed” fires in Basecamp, Nodest will update matching rows in Google Sheets.
When “To-do completed” fires in Basecamp, Nodest will update matching rows in Google Sheets.
When “To-do completed” fires in Basecamp, Nodest will create a row in Google Sheets.
When “To-do created” fires in Basecamp, Nodest will create a row in Google Sheets.
When “Comment added” fires in Todoist, Nodest will send a prompt in Gemini and create a row in Google Sheets.
When “Comment added” fires in Todoist, Nodest will send a prompt in OpenAI and create a row in Google Sheets.
When “Project deleted” fires in Todoist, Nodest will delete a sheet in Google Sheets.
When “Project archived” fires in Todoist, Nodest will copy a sheet to a spreadsheet in Google Sheets.
When “Project created” fires in Todoist, Nodest will add a sheet to a spreadsheet in Google Sheets.
When “Project created” fires in Todoist, Nodest will create a spreadsheet in Google Sheets.
When “Project created” fires in Todoist, Nodest will create a row in Google Sheets.
When “Reminder fired” fires in Todoist, Nodest will create a row in Google Sheets.
When “Comment added” fires in Todoist, Nodest will create a row in Google Sheets.
When “Task deleted” fires in Todoist, Nodest will clear a row in Google Sheets.
When “Task deleted” fires in Todoist, Nodest will delete a row in Google Sheets.
When “Task updated” fires in Todoist, Nodest will update a row in Google Sheets.
When “Task uncompleted” fires in Todoist, Nodest will update matching rows in Google Sheets.
When “Task updated” fires in Todoist, Nodest will update matching rows in Google Sheets.
When “Task completed” fires in Todoist, Nodest will update matching rows in Google Sheets.
When “Task completed” fires in Todoist, Nodest will create a row in Google Sheets.
When “Task created” fires in Todoist, Nodest will create a row in Google Sheets.
When “Note created” fires in Pipedrive, Nodest will create a row in Google Sheets.
When “Lead created” fires in Pipedrive, Nodest will create a row in Google Sheets.
When “Activity created” fires in Pipedrive, Nodest will create a row in Google Sheets.
When “Organization created” fires in Pipedrive, Nodest will create a row in Google Sheets.
When “Person updated” fires in Pipedrive, Nodest will update matching rows in Google Sheets.
When “Person created” fires in Pipedrive, Nodest will create a row in Google Sheets.
When “Deal lost” fires in Pipedrive, Nodest will create a row in Google Sheets.
When “Deal won” fires in Pipedrive, Nodest will create a row in Google Sheets.
When “Deal stage changed” fires in Pipedrive, Nodest will update matching rows in Google Sheets.
When “Deal created” fires in Pipedrive, Nodest will create a row in Google Sheets.
When “Conversation closed” fires in Intercom, Nodest will send a prompt in Gemini and create a row in Google Sheets.
When “Conversation closed” fires in Intercom, Nodest will send a prompt in OpenAI and create a row in Google Sheets.
When “Company created” fires in Intercom, Nodest will create a row in Google Sheets.
When “Contact unsubscribed” fires in Intercom, Nodest will create a row in Google Sheets.
When “Event tracked” fires in Intercom, Nodest will create a row in Google Sheets.
When “Ticket rated” fires in Intercom, Nodest will create a row in Google Sheets.
When “Conversation rated” fires in Intercom, Nodest will create a row in Google Sheets.
When “Ticket state updated” fires in Intercom, Nodest will update matching rows in Google Sheets.
When “Ticket created” fires in Intercom, Nodest will create a row in Google Sheets.
When “Conversation closed” fires in Intercom, Nodest will update matching rows in Google Sheets.
When “Conversation created” fires in Intercom, Nodest will create a row in Google Sheets.
When “User updated” fires in Intercom, Nodest will update matching rows in Google Sheets.
When “Lead created” fires in Intercom, Nodest will create a row in Google Sheets.
When “User created” fires in Intercom, Nodest will create a row in Google Sheets.
When “Meeting recap created” fires in Calendly, Nodest will create a row in Google Sheets.
When “Contact created” fires in Calendly, Nodest will create a row in Google Sheets.
When “Routing form submitted” fires in Calendly, Nodest will create a row in Google Sheets.
When “Invitee marked as no-show” fires in Calendly, Nodest will update matching rows in Google Sheets.
When “Invitee canceled” fires in Calendly, Nodest will update matching rows in Google Sheets.
When “Invitee created” fires in Calendly, Nodest will create a row in Google Sheets.
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 “Subscription created” fires in MemberPress, Nodest will create a row in Google Sheets.
When “Subscription stopped” fires in MemberPress, Nodest will create a row in Google Sheets.
When “Subscription paused” fires in MemberPress, Nodest will create a row in Google Sheets.
When “Document created” fires in Linear, Nodest will create a row in Google Sheets.
When “Project update posted” fires in Linear, Nodest will create a row in Google Sheets.
When “Page moved into database” fires in Notion, Nodest will create a row in Google Sheets.
When “Page content updated” fires in Notion, Nodest will create a row in Google Sheets.
When “Property changed” fires in Notion, Nodest will create a row in Google Sheets.
When “Property changed” fires in Notion, Nodest will update a row in Google Sheets.
When “Member joined workspace” fires in Slack, Nodest will create a row in Google Sheets.
When “Bot received a direct message” fires in Slack, Nodest will create a row in Google Sheets.
When “Reaction added” fires in Slack, Nodest will create a row in Google Sheets.
When “Bot mentioned” fires in Slack, Nodest will create a row in Google Sheets.
When “Message posted” fires in Slack, Nodest will create a row in Google Sheets.
When “Subitem created” fires in Monday.com, Nodest will create a row in Google Sheets.
When “Item deleted” fires in Monday.com, Nodest will create a row in Google Sheets.
When “Item moved to group” fires in Monday.com, Nodest will create a row in Google Sheets.
When “Update posted” fires in Monday.com, Nodest will create a row in Google Sheets.
When “Column value changed” fires in Monday.com, Nodest will create a row in Google Sheets.
When “Status changed” fires in Monday.com, Nodest will create a row in Google Sheets.
When “Status changed” fires in Monday.com, Nodest will update a row in Google Sheets.
When “Item created” fires in Monday.com, Nodest will create a row in Google Sheets.
When “Member email changed” fires in Mailchimp, Nodest will create a row in Google Sheets.
When “Member profile updated” fires in Mailchimp, Nodest will create a row in Google Sheets.
When “Campaign sent” fires in Mailchimp, Nodest will create a row in Google Sheets.
When “Member cleaned” fires in Mailchimp, Nodest will create a row in Google Sheets.
When “Member unsubscribed” fires in Mailchimp, Nodest will create a row in Google Sheets.
When “Member subscribed” fires in Mailchimp, Nodest will create a row in Google Sheets.
When “Task deleted” fires in Asana, Nodest will create a row in Google Sheets.
When “Comment added” fires in Asana, Nodest will create a row in Google Sheets.
When “Task updated” fires in Asana, Nodest will create a row in Google Sheets.
When “Task updated” fires in Asana, Nodest will update a row in Google Sheets.
When “Task completed” fires in Asana, Nodest will create a row in Google Sheets.
When “Task created” fires in Asana, Nodest will create a row in Google Sheets.
When “List created” fires in ClickUp, Nodest will create a row in Google Sheets.
When “Task tag changed” fires in ClickUp, Nodest will create a row in Google Sheets.
When “Task deleted” fires in ClickUp, Nodest will create a row in Google Sheets.
When “Task moved” fires in ClickUp, Nodest will create a row in Google Sheets.
When “Task due date changed” fires in ClickUp, Nodest will create a row in Google Sheets.
When “Task assignee changed” fires in ClickUp, Nodest will create a row in Google Sheets.
When “Comment posted on a task” fires in ClickUp, Nodest will create a row in Google Sheets.
When “Task status changed” fires in ClickUp, Nodest will create a row in Google Sheets.
When “Task status changed” fires in ClickUp, Nodest will update a row in Google Sheets.
When “Task created” fires in ClickUp, Nodest will create a row in Google Sheets.
When “Comment posted” fires in WordPress, Nodest will send a prompt in Gemini and create a row in Google Sheets.
When “Comment posted” fires in WordPress, Nodest will send a prompt in OpenAI and create a row in Google Sheets.
When “Page published” fires in WordPress, Nodest will create a row in Google Sheets.
When “Post published” fires in WordPress, Nodest will create a row in Google Sheets.
When “Comment posted” fires in WordPress, Nodest will create a row in Google Sheets.
When “User registered” fires in WordPress, Nodest will create a row in Google Sheets.
When “Customer created” fires in WooCommerce, Nodest will create a row in Google Sheets.
When “Payment complete” fires in WooCommerce, Nodest will create a row in Google Sheets.
When “Order status changed” fires in WooCommerce, Nodest will create a row in Google Sheets.
When “Order status changed” fires in WooCommerce, Nodest will update a row in Google Sheets.
When “Order placed” fires in WooCommerce, Nodest will create a row in Google Sheets.
When “Suppression added” fires in Resend, Nodest will create a row in Google Sheets.
When “Contact deleted” fires in Resend, Nodest will create a row in Google Sheets.
When “Contact updated” fires in Resend, Nodest will create a row in Google Sheets.
When “Contact created” fires in Resend, Nodest will create a row in Google Sheets.
When “Email received” fires in Resend, Nodest will create a row in Google Sheets.
When “Email marked as spam” fires in Resend, Nodest will create a row in Google Sheets.
When “Email failed” fires in Resend, Nodest will create a row in Google Sheets.
When “Email bounced” fires in Resend, Nodest will create a row in Google Sheets.
When “Email clicked” fires in Resend, Nodest will create a row in Google Sheets.
When “Email opened” fires in Resend, Nodest will create a row in Google Sheets.
When “Email delivered” fires in Resend, Nodest will create a row in Google Sheets.
When “Page created” fires in Notion, Nodest will create a row in Google Sheets.
When “Payment refunded” fires in MemberPress, Nodest will create a row in Google Sheets.
When “Payment failed” fires in MemberPress, Nodest will create a row in Google Sheets.
When “Member added” fires in MemberPress, Nodest will create a row in Google Sheets.
When “Member signed up” fires in MemberPress, Nodest will create a row in Google Sheets.
When “Payment completed” fires in MemberPress, Nodest will create a row in Google Sheets.
When “Issue label created” fires in Linear, Nodest will create a row in Google Sheets.
When “Comment updated” fires in Linear, Nodest will create a row in Google Sheets.
When “Comment created” fires in Linear, Nodest will create a row in Google Sheets.
When “Cycle updated” fires in Linear, Nodest will create a row in Google Sheets.
When “Cycle created” fires in Linear, Nodest will create a row in Google Sheets.
When “Project updated” fires in Linear, Nodest will create a row in Google Sheets.
When “Project created” fires in Linear, Nodest will create a row in Google Sheets.
When “Issue removed” fires in Linear, Nodest will create a row in Google Sheets.
When “Issue updated” fires in Linear, Nodest will update a row in Google Sheets.
When “Issue updated” fires in Linear, Nodest will create a row in Google Sheets.
When “Issue created” fires in Linear, Nodest will create a row in Google Sheets.
When “Form submitted” fires in Gravity Forms, Nodest will send a prompt in Gemini and create a row in Google Sheets.
When “Form submitted” fires in Gravity Forms, Nodest will send a prompt in OpenAI and create a row in Google Sheets.
When “Form submitted” fires in Gravity Forms, Nodest will create a row in Google Sheets.
When “Form submitted” fires in Fluent Forms, Nodest will send a prompt in Gemini and create a row in Google Sheets.
When “Form submitted” fires in Fluent Forms, Nodest will send a prompt in OpenAI and create a row in Google Sheets.
When “Entry deleted” fires in Fluent Forms, Nodest will create a row in Google Sheets.
When “Note added to entry” fires in Fluent Forms, Nodest will create a row in Google Sheets.
When “Payment refunded” fires in Fluent Forms, Nodest will create a row in Google Sheets.
When “Subscription cancelled” fires in Fluent Forms, Nodest will create a row in Google Sheets.
When “Subscription payment received” fires in Fluent Forms, Nodest will create a row in Google Sheets.
When “Payment status changed” fires in Fluent Forms, Nodest will create a row in Google Sheets.
When “Partial submission saved” fires in Fluent Forms, Nodest will create a row in Google Sheets.
When “Entry status changed” fires in Fluent Forms, Nodest will create a row in Google Sheets.
When “Entry status changed” fires in Fluent Forms, Nodest will update a row in Google Sheets.
When “Form submitted” fires in Fluent Forms, Nodest will create a row in Google Sheets.
When “File downloaded” fires in Easy Digital Downloads, Nodest will create a row in Google Sheets.
When “Download published” fires in Easy Digital Downloads, Nodest will create a row in Google Sheets.
When “Customer created” fires in Easy Digital Downloads, Nodest will create a row in Google Sheets.
When “Purchase completed” fires in Easy Digital Downloads, Nodest will create a row in Google Sheets.
When “Transactional email marked as spam” fires in Brevo, Nodest will create a row in Google Sheets.
When “Transactional email hard bounced” fires in Brevo, Nodest will create a row in Google Sheets.
When “Transactional email soft bounced” fires in Brevo, Nodest will create a row in Google Sheets.
When “Transactional email blocked” fires in Brevo, Nodest will create a row in Google Sheets.
When “Transactional email clicked” fires in Brevo, Nodest will create a row in Google Sheets.
When “Transactional email opened” fires in Brevo, Nodest will create a row in Google Sheets.
When “Transactional email delivered” fires in Brevo, Nodest will create a row in Google Sheets.
When “Transactional email sent” fires in Brevo, Nodest will create a row in Google Sheets.
When “Marketing email marked as spam” fires in Brevo, Nodest will create a row in Google Sheets.
When “Marketing email hard bounced” fires in Brevo, Nodest will create a row in Google Sheets.
When “Marketing email soft bounced” fires in Brevo, Nodest will create a row in Google Sheets.
When “Marketing email clicked” fires in Brevo, Nodest will create a row in Google Sheets.
When “Marketing email opened” fires in Brevo, Nodest will create a row in Google Sheets.
When “Marketing email delivered” fires in Brevo, Nodest will create a row in Google Sheets.
When “Contact updated” fires in Brevo, Nodest will create a row in Google Sheets.
When “Contact deleted” fires in Brevo, Nodest will create a row in Google Sheets.
When “Contact unsubscribed” fires in Brevo, Nodest will create a row in Google Sheets.
When “Contact added to list” fires in Brevo, Nodest will create a row in Google Sheets.
When “Campaign sent” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “Email bounced” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “Email opened” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “Link clicked” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “SMS reply received” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “Email replied” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “Contact updated” fires in ActiveCampaign, Nodest will update a row in Google Sheets.
When “Contact unsubscribed from list” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “Contact subscribed to list” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “Deal task created” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “Deal note added” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
When “Deal updated” fires in ActiveCampaign, Nodest will update a row in Google Sheets.
When “Deal created” fires in ActiveCampaign, Nodest will create a row in Google Sheets.
Sign up for free and start building in minutes.
