Automate Google Drive to Slack Notifications with Latenode

Automate Google Drive Updates with Slack Notifications Using Latenode

Do you want Slack updates for files added or modified on Google Drive? Learn how to automate this process on Latenode in minutes. This could revolutionize your workflow, creating advanced automations with flexible logic, an AI assistant, JavaScript, and a headless browser for ultimate control. Save up to 90% compared to other competitors. Registration is straightforward; sign up today with no credit card required and start creating automations that save you time and money.

Getting Started with Latenode

Transform your workflow with Latenode. Let's create a new scenario on the Latenode platform. This scenario will be triggered when a file is added or modified on Google Drive and send a message to the appropriate Slack channel, indicating that the file has been successfully added or modified.

First, click the 'Create New Scenario' button. Name the new scenario appropriately for future reference and save the changes.

Adding the Trigger Node

To execute the scenario, we need to add two nodes. The first node is a trigger and is required to start the scenario when a file is added to Google Drive. Find the required group of nodes; we are interested in Google Drive and the 'New or Modified Files' node from the trigger group.

To configure the node, you need to establish a connection. Click the 'New Authorization' button, select the Google service, and the necessary Google Drive connection. Authorize using an existing Google account. Select the account and grant the necessary permissions to the Latenode platform. Once authorized, fill in the required fields in the node and click 'Save.' The trigger node has been added.

Adding the Action Node

Let's add another node. This one belongs to the action nodes group. We are interested in Slack, specifically the Slackbot group. One of the action nodes is for sending a message to a public channel. Select it.

To configure the node, you also need to establish a connection. There are three possible connection options, but let's try to connect using an access token. You need to create an application on the Slack website. Follow the necessary link and click the 'Create New Application' button.

In the modal window, choose the 'From Scratch' parameters and add the application name, e.g., 'Latenode Bot,' and select the necessary workspace. Before creating the application, you need to have at least one workspace in Slack. Add the necessary permissions and scopes for the bot.

The bot should have the rights to read the channel and send messages to it. After all necessary scopes have been added, confirm the installation of the application in the workspace. Confirm the permissions and obtain the necessary token. Copy it and return to Latenode. Select the access token service and enter the obtained token in the field. Click the 'Authorization' button.

After authorization, fields that need to be filled in will be visible. Among these, two are mandatory: the field for selecting the channel, e.g., 'docs,' and the field for entering the message text to be sent to the channel. Add a message indicating that the file was created or modified and click 'Save.'

Completing the Bot Setup

To complete the bot setup in Slack, you need to send a message to the desired channel like 'invite @botname', where 'botname' is the name of the application you created. Select the application name and send the message. The bot has been added to the necessary channel.

Return to the Latenode platform. After all the settings have been made and the scenario has been saved, run it once to start the scenario. Add a file to Google Drive. Wait for the changes to be saved and return to the Latenode platform. We can see the successfully executed scenario.

Each node in the scenario has output data, including, for example, the 'New or Modified Files' node, which provides data about the modified or created file, such as its name or identifier. The node for sending messages to Slack informs us that the message has been successfully sent and, for example, provides its text.

Testing the Automation

Let's see what happened in Slack. A message indicating that a file was added to Google Drive was successfully sent. Let's try to modify the message to include the file name from the Google Drive node. To do this, select the field displaying the message text, click on the desired place in the text, and select the parameter from the previous node in the auxiliary window. Save the changes, save the entire scenario, and run it again. Change the file name, wait for the changes to be saved, and return to the platform. We can see the completed scenario with a new message, including the file name provided by the Google Drive node.

Let's go to Slack. A new message has also been sent to the required 'docs' channel in Slack. Thus, we have created a scenario that sends a message to the required Slack channel using the created bot when a new file is created or an existing file is modified on Google Drive.