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

Add the Microsoft To Do Node
Select the Microsoft To Do node from the app selection panel on the right.

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

Microsoft To Do
⚙
Feedly
Authenticate Feedly
Now, click the Feedly node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Feedly settings. Authentication allows you to use Feedly through Latenode.
Configure the Microsoft To Do and Feedly 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 Microsoft To Do and Feedly 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
⚙
Feedly
Trigger on Webhook
⚙
Microsoft To Do
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Microsoft To Do, Feedly, 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 Microsoft To Do and Feedly integration works as expected. Depending on your setup, data should flow between Microsoft To Do and Feedly (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Microsoft To Do and Feedly
Feedly + Microsoft To Do + Microsoft Teams: When a new article appears in a watched Feedly feed, a task is created in Microsoft To Do. A message containing the article link is then sent to a specified Microsoft Teams channel.
Feedly + Microsoft To Do + Gmail: When a new article appears in a watched Feedly feed, it's added as a task to a specified Microsoft To Do list. A summary email containing the links to the created tasks is then sent via Gmail.
Microsoft To Do and Feedly integration alternatives
About Microsoft To Do
Automate task management by integrating Microsoft To Do with Latenode. Automatically create tasks from emails, database entries, or other apps. Sync tasks between systems, set reminders based on triggers, and manage projects visually using Latenode's low-code interface. Stop manual updates and build scalable task workflows.
Related categories
About Feedly
Aggregate and filter Feedly articles within Latenode to automate content-driven workflows. Track brand mentions, industry trends, or competitor activity, then instantly trigger actions like posting to social media, updating databases, or notifying teams—all based on custom rules and logic.
Similar apps
Related categories
See how Latenode works
FAQ Microsoft To Do and Feedly
How can I connect my Microsoft To Do account to Feedly using Latenode?
To connect your Microsoft To Do account to Feedly on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Microsoft To Do and click on "Connect".
- Authenticate your Microsoft To Do and Feedly accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I create tasks from Feedly articles?
Yes, you can! Latenode enables creating tasks in Microsoft To Do directly from Feedly articles, streamlining your workflow. Automatically manage your reading list and task management efficiently.
What types of tasks can I perform by integrating Microsoft To Do with Feedly?
Integrating Microsoft To Do with Feedly allows you to perform various tasks, including:
- Create a Microsoft To Do task for each newly saved Feedly article.
- Update task due dates in Microsoft To Do based on Feedly article dates.
- Add Feedly article titles to Microsoft To Do task descriptions.
- Automatically complete tasks when the related article is read.
- Trigger custom notifications based on updates in both apps.
How do I handle errors in my Microsoft To Do Latenode workflow?
Latenode offers advanced error handling. You can set up alerts, retry failed tasks, and log detailed errors to ensure reliable automation.
Are there any limitations to the Microsoft To Do and Feedly integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by Microsoft To Do and Feedly APIs may affect performance.
- Custom field syncing beyond basic titles and descriptions is not supported.
- Complex conditional logic may require JavaScript code blocks.