Skip to content

Connections

After setting up the second component, youโ€™ll notice we now have two unconnected components in the editor, as shown below. To ensure the automation runs in the correct order, we need to connect these components so Monkedo understands the flow of actions.

Two unconnected components

Components are connected by linking the output of one component to the input of the next. Input ports are located on the left side of a component block, while output ports are on the right. In this case, we have an output from the Schedule Trigger but no visible input on the Get Values component. This occurs when all the componentโ€™s inputs are set directly through the Info Panel, meaning no inputs are sourced from the automation flow.

To resolve this, you can create an activation input on the Get Values component to allow it to connect to other components. Click the Get Values component and look for the Add Activation Input option at the bottom of the input list. Clicking this option will create an activation input and display a connection port on the component, as shown below.

Activation input on a component
Activation input on a component

This activation input doesnโ€™t accept any parametersโ€”itโ€™s solely used to create a connection point between components. Now, you can link the Schedule Trigger to the Get Values component. Click and hold on the output port of the Schedule Trigger, then drag your mouse to the input port you just created on the Get Values component. Release the mouse to create the connection. This connection tells Monkedo that after the automation is triggered by the Schedule Trigger, it should proceed to the Get Values component to retrieve the tweet content from the file.

Components connected to each other

Whatโ€™s Next?

Up until now, we added trigger and action components, configured the inputs and connected them together. In the next article, weโ€™ll explore how to check if there is new content for the current day in the table.