openclaw - 💡(How to fix) Fix Mission Control: 'Configure API Key' button on Integrations page does nothing [1 comments, 1 participants]

On the Mission Control Integrations page, each integration card (e.g. Perplexity Web Search, Google Workspace CLI) has a "Configure API Key" button. Clicking it does nothing — no modal, no redirect, no error message. 3. At minimum, display a helpful error if the setup can't proceed (e.g. missing dependencies like gcloud for GWS) 4. Nothing happens — no visual feedback, no error

Fix Plan

The fix involves wiring up the "Configure API Key" button to trigger the corresponding gateway API endpoint or an interactive configuration flow.

Step-by-Step Solution:

1. Verify the API endpoint: Ensure the gateway API endpoint for configuring API keys exists and is correctly defined.
2. Update the button's click handler: Modify the button's click event handler to make a request to the API endpoint or trigger the interactive flow.
3. Implement error handling: Add error handling to display helpful messages if the setup can't proceed.

Example Code:

// Assuming a React component for the integration card
import React from 'react';
import axios from 'axios';

const IntegrationCard = () => {
  const handleConfigureClick = async () => {
    try {
      // Replace with the actual API endpoint URL
      const response = await axios.post('https://localhost:18789/api/configure-api-key');
      // Handle successful response
      if (response.status === 200) {
        // Trigger interactive flow or display success message
      }
    } catch (error) {
      // Handle error and display helpful message
      if (error.response.status === 400) {
        // Display error message indicating missing dependencies or invalid input
      } else {
        // Display generic error message
      }
    }
  };

  return (
    <div>
      <button onClick={handleConfigureClick}>⚡ Configure API Key</button>
    </div>
  );
};

Verification

To verify the fix, follow these steps:

• Click the "Configure API Key" button on an unconfigured integration card.
• Verify that the button triggers the expected behavior (interactive flow, modal, or error message).
• Test with different scenarios (e.g., missing dependencies, invalid input) to ensure error handling works correctly.

Extra Tips

• Ensure the API endpoint is properly secured and validated to prevent unauthorized access or malicious input.
• Consider adding logging to track button clicks and errors for future debugging and analytics.