My Slack Buttons Show "App Has Not Been Configured for This Feature" — What Do I Do?

Last updated: April 14, 2026

Gumloop can send Slack messages with Block Kit buttons, but it cannot process button click callbacks yet. When someone clicks a button in a message sent by Gumloop, Slack shows "App has not been configured for this feature." Use thread replies instead of buttons to collect responses.

Symptoms

  • You send a Slack message with buttons using the Slack Block Kit Sender node or your agent's Slack tools.

  • When someone clicks a button, Slack shows the error: App has not been configured for this feature. Please contact the app's developer.

  • The button click does nothing — no workflow runs, no data is captured.

Cause

The Slack Block Kit Sender can build and send messages containing buttons, but Gumloop does not currently have a handler for custom button click actions. Slack requires an interactivity endpoint that processes each button's action_id when clicked — Gumloop's backend only handles its own internal help button, not user-defined buttons.

This means you can display buttons for visual layout, but they won't trigger any action when clicked. This is a known limitation and interactive button support is on the roadmap.

Workaround: Use Thread Replies Instead of Buttons

Instead of asking users to click a button, ask them to reply in the thread. Gumloop can monitor thread replies and take action based on what someone writes.

Option 1: Use an Agent with Slack Tools

Deploy an agent to Slack and have it monitor threads for replies. Slack agents can automatically check for new responses and react accordingly.

Option 2: Use the Slack Message Reader in a Workflow

If you're using workflows instead of agents, the Slack Message Reader node can read thread replies.

  1. Send your initial message with the Slack Block Kit Sender (you can still use rich formatting — just skip the buttons, or include them as visual-only elements).

  2. Capture the Thread ID from the sent message output.

  3. Use the Slack Message Reader node with the "Read Full Thread?" option enabled to fetch all replies to that thread.

  4. Process the replies with downstream nodes — check for keywords, tag people, update other platforms, etc.

To run this on a schedule (e.g., check for replies every 7 days), use a scheduled trigger that kicks off the workflow at your desired interval.

What About Link Buttons?

If your goal is just to send users to a URL (not trigger a Gumloop action), you can use Block Kit buttons with a url field. These are link buttons — they open the URL in the user's browser and do not require an interactivity handler. Only action buttons (ones that need a server-side callback) hit this limitation.

Still Need Help?

If this didn't resolve your issue, reach out to support at support@gumloop.com.

Related Docs