How to connect Google AppSheet and Wrike
Create a New Scenario to Connect Google AppSheet and Wrike
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Google AppSheet, triggered by another scenario, or executed manually (for testing purposes). In most cases, Google AppSheet or Wrike will be your first step. To do this, click "Choose an app," find Google AppSheet or Wrike, and select the appropriate trigger to start the scenario.

Add the Google AppSheet Node
Select the Google AppSheet node from the app selection panel on the right.

Google AppSheet
Configure the Google AppSheet
Click on the Google AppSheet node to configure it. You can modify the Google AppSheet URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Wrike Node
Next, click the plus (+) icon on the Google AppSheet node, select Wrike from the list of available apps, and choose the action you need from the list of nodes within Wrike.

Google AppSheet
⚙

Wrike

Authenticate Wrike
Now, click the Wrike node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Wrike settings. Authentication allows you to use Wrike through Latenode.
Configure the Google AppSheet and Wrike Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Google AppSheet and Wrike Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙

Wrike
Trigger on Webhook
⚙
Google AppSheet
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Google AppSheet, Wrike, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Google AppSheet and Wrike integration works as expected. Depending on your setup, data should flow between Google AppSheet and Wrike (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Google AppSheet and Wrike
Google AppSheet + Wrike + Slack: When a new record is added in Google AppSheet, a task is created in Wrike. Then, a notification is sent to a Slack channel to inform the team about the new task.
Wrike + Google AppSheet + Google Sheets: When a task is completed in Wrike, the corresponding record in Google AppSheet is updated with the new status. This update is then logged in Google Sheets for reporting purposes.
Google AppSheet and Wrike integration alternatives
About Google AppSheet
Use Google AppSheet for no-code app creation and connect it to Latenode to automate back-end tasks. Trigger workflows on AppSheet events to update databases, send notifications, or process data. Centralize logic in Latenode, bypassing AppSheet limits and adding advanced features like AI, file parsing, or custom integrations via API and code.
Similar apps
Related categories

About Wrike
Automate Wrike project updates and task assignments directly from other apps using Latenode. Sync data between Wrike and your CRM, database, or calendar. Create custom triggers based on project status changes and automate reporting. Latenode provides flexible integration with no-code tools or custom JavaScript, allowing you to tailor Wrike workflows without step limits.
Related categories
See how Latenode works
FAQ Google AppSheet and Wrike
How can I connect my Google AppSheet account to Wrike using Latenode?
To connect your Google AppSheet account to Wrike on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google AppSheet and click on "Connect".
- Authenticate your Google AppSheet and Wrike accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automate project status updates from Google AppSheet to Wrike?
Yes, you can! Latenode allows real-time data sync, so project updates automatically flow from Google AppSheet to Wrike, improving team visibility and reducing manual reporting efforts.
What types of tasks can I perform by integrating Google AppSheet with Wrike?
Integrating Google AppSheet with Wrike allows you to perform various tasks, including:
- Create new Wrike tasks from Google AppSheet form submissions.
- Update Wrike task statuses based on Google AppSheet data changes.
- Sync Google AppSheet data entries as Wrike project portfolio items.
- Trigger Wrike project creation from new Google AppSheet entries.
- Send notifications in Wrike based on Google AppSheet rule triggers.
What Google AppSheet data can I access within my Latenode workflows?
You can access any data available in your Google AppSheet apps, including rows, columns, and calculated values, for seamless automation.
Are there any limitations to the Google AppSheet and Wrike integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require custom JavaScript code.
- Real-time synchronization is subject to Google AppSheet and Wrike API rate limits.
- Historical data migration between the two platforms needs separate handling.