How to connect Google contacts and Userback
Create a New Scenario to Connect Google contacts and Userback
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 contacts, triggered by another scenario, or executed manually (for testing purposes). In most cases, Google contacts or Userback will be your first step. To do this, click "Choose an app," find Google contacts or Userback, and select the appropriate trigger to start the scenario.

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


Google contacts

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


Google contacts
⚙
Userback

Authenticate Userback
Now, click the Userback node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Userback settings. Authentication allows you to use Userback through Latenode.
Configure the Google contacts and Userback 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 contacts and Userback 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
⚙
Userback
Trigger on Webhook
⚙

Google contacts
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Google contacts, Userback, 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 contacts and Userback integration works as expected. Depending on your setup, data should flow between Google contacts and Userback (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Google contacts and Userback
Google Contacts + Userback + Slack: When a new contact is added to Google Contacts, a feedback request is created in Userback, and a notification is sent to a Slack channel.
Userback + Google Contacts + Gmail: When new feedback is received in Userback, the automation finds the contact in Google Contacts and sends a thank you email via Gmail.
Google contacts and Userback integration alternatives

About Google contacts
Sync Google Contacts with Latenode to automate contact management. Update records, trigger follow-ups, or enrich profiles based on events in other apps. Avoid manual data entry; use Latenode’s visual builder to create flows that sync contacts across your marketing and sales tools, adding custom logic without coding.
Similar apps
Related categories
About Userback
Use Userback in Latenode to automate feedback loops. Collect user feedback, then trigger actions based on sentiment or keywords. Route bug reports, feature requests, and support queries directly into your workflows. Close the loop faster and with greater accuracy than standalone solutions.
Related categories
See how Latenode works
FAQ Google contacts and Userback
How can I connect my Google contacts account to Userback using Latenode?
To connect your Google contacts account to Userback on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Google contacts and click on "Connect".
- Authenticate your Google contacts and Userback accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Userback feedback items from new Google contacts?
Yes, you can! Latenode allows automated workflows, creating Userback items from new Google contacts. This ensures all new contacts are immediately considered for feedback, improving product development.
What types of tasks can I perform by integrating Google contacts with Userback?
Integrating Google contacts with Userback allows you to perform various tasks, including:
- Automatically creating Userback users from new Google contacts.
- Updating Userback user details when Google contacts are updated.
- Triggering Userback feedback requests based on contact properties.
- Segmenting Userback feedback by Google contact group memberships.
- Sending personalized feedback requests using Google contacts data.
Can I filter Google contacts before creating Userback feedback items?
Yes, using Latenode's logic blocks, you can filter Google contacts based on criteria before creating Userback feedback items for specific segments.
Are there any limitations to the Google contacts and Userback integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by Google contacts and Userback APIs may affect large-scale operations.
- Custom field mapping requires familiarity with data structures in both applications.
- Real-time synchronization is not guaranteed; delays may occur depending on workload.