Flowground决策模块实现及Microsoft Graph API集成问询

Hey Max, let's tackle your two questions one by one to get your Flowground setup working exactly how you need it:

Right now your setup is firing all channels at once, but we can fix that with conditional branching in Flowground. Here's how to do it step by step:

Option 1: Use Built-in Condition Components #

Flowground has native condition nodes that let you route your workflow based on input values:

• Drag a Condition node right after your telekom/webhook component that pulls in the department variable.
• Set the first condition rule to department equals "Backoffice".
• Connect the "True" path of this condition to your telekom/rest-api-component configured for the "Account Management" Teams channel.
• Repeat this pattern for other department values: add more condition rules or nested condition nodes, each linking to their respective channel's API component.
• For any unrecognized department values, you can add a "Default" path to either skip sending or route to a fallback channel.

Option 2: Use Custom Script for Flexible Routing #

If you need more complex logic (like handling a long list of departments), use a Custom JavaScript component instead:

// Grab the incoming department value from your workflow data
const dept = $input.department;
let targetChannelId = "";

// Map department values to your configured API component IDs
switch(dept) {
  case "Backoffice":
    targetChannelId = "account-mgmt-api-component"; // Replace with your actual component ID
    break;
  case "Finance":
    targetChannelId = "finance-api-component";
    break;
  case "IT":
    targetChannelId = "it-api-component";
    break;
  default:
    targetChannelId = "default-api-component"; // Fallback channel
}

// Pass the target ID to the next steps
return { targetChannel: targetChannelId };

Then, for each of your telekom/rest-api-component nodes, set an Execution Condition like $input.targetChannel equals "your-component-id". Only the component matching the target ID will fire, so you won't get simultaneous sends anymore.

Don't Forget to Test! #

After setting up the branching, test with different department values to make sure only the intended channel receives the message card. It's easy to miss a condition rule, so quick validation will save you headaches later.

Great question—right now, Flowground doesn't have an official Microsoft Graph API module. But the good news is that the product team is actively evaluating adding Office 365 ecosystem integrations based on user feedback.

If this is critical for your workflows, I'd recommend submitting a feature request through Flowground's in-app feedback tool. Be specific about which Graph API endpoints you need (like Teams message sending, user management, or calendar operations) — the more details you provide, the higher priority it'll get.

In the meantime, you can use Flowground's Generic HTTP Request component to call Graph API directly:

1. Register an app in Azure AD to get an access token (make sure to grant the necessary permissions for Teams/Office 365 actions).
2. Add an HTTP component to your workflow, set the request URL to the Graph API endpoint you need (e.g., https://graph.microsoft.com/v1.0/teams/{team-id}/channels/{channel-id}/messages).
3. Configure the request headers to include Authorization: Bearer {your-access-token}.
4. Build your message card payload according to Graph API's schema and send it via the POST method.

This workaround will let you integrate with Office 365 apps while you wait for an official module.

内容的提问来源于stack exchange，提问作者Max Haberl