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

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

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

Inoreader
⚙

Google contacts

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

Google contacts
Trigger on Webhook
⚙
Inoreader
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Inoreader, Google contacts, 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 Inoreader and Google contacts integration works as expected. Depending on your setup, data should flow between Inoreader and Google contacts (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Inoreader and Google contacts
Inoreader + Google Contacts + Slack: When a new article appears in a specific Inoreader folder, the automation will list all Google Contacts and send them a direct message via Slack with a summary of the article.
Google Contacts + Inoreader + Google Sheets: When a new contact is added to Google Contacts, the automation searches Inoreader for news articles containing the contact's name and logs the article titles and links in a Google Sheet.
Inoreader and Google contacts integration alternatives
About Inoreader
Aggregate and filter news feeds in Inoreader, then use Latenode to automate actions based on specific articles. Trigger alerts, update databases, or post to social media directly from your curated content. Use Latenode's visual editor and JavaScript node to refine filtering and formatting rules far beyond Inoreader's native options.
Similar apps
Related categories

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
See how Latenode works
FAQ Inoreader and Google contacts
How can I connect my Inoreader account to Google contacts using Latenode?
To connect your Inoreader account to Google contacts on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Inoreader and click on "Connect".
- Authenticate your Inoreader and Google contacts accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically add new Inoreader subscribers to Google contacts?
Yes, you can! Latenode's visual editor makes it simple to create this automation. Easily grow your contact list and engage new readers with personalized outreach campaigns.
What types of tasks can I perform by integrating Inoreader with Google contacts?
Integrating Inoreader with Google contacts allows you to perform various tasks, including:
- Add new Inoreader subscribers as Google contacts automatically.
- Update contact information in Google contacts from Inoreader feeds.
- Create Google contacts from Inoreader articles matching specific criteria.
- Trigger email campaigns via Google contacts for new Inoreader content.
- Sync Inoreader subscription data with Google contacts groups.
HowsecureisInoreaderconnectionwithGooglecontactsonLatenode?
Latenode uses secure authentication protocols to protect your data, ensuring your Inoreader and Google contacts accounts are safely connected.
Are there any limitations to the Inoreader and Google contacts integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by Inoreader and Google contacts APIs may affect performance.
- Complex data transformations may require JavaScript coding.
- Initial synchronization of large contact lists might take some time.