- Overview
- Configuration
Miro
Streamline team collaboration with ADManager Plus-Miro integration
Miro is an online whiteboard platform that enables real-time team collaboration by providing a visual workspace for brainstorming, planning, and project management. Integrating Miro with ADManager Plus enhances collaboration by enabling IT administrators to create Miro boards and enforce sharing policies directly from ADManager Plus.
Automated board creation
Create Miro boards with specified names and sharing policies directly from ADManager Plus. This ensures that boards are set up with the correct configurations and access permissions from the outset, improving operational efficiency.
Need assistance to integrate Workable with ADManager Plus?
Configuration Document: Integrating Miro with ADManager Plus
Prerequisites
Miro uses OAuth 2.0 to authorize API requests.
It requires a client_id and client_secret for authorization.
Privileges
To import users (inbound action): Ensure the account used for authorization has permission to read all user accounts.
To perform any action or query in Miro (outbound action): Ensure the account used for authorization has permission to perform the desired action.
Note: ADManager Plus comes with preconfigured set of APIs that help perform basic actions with the integration. If the action you require is not available, please gather the necessary API details from Miro's API documentation to configure inbound or outbound webhooks to perform the required actions.Authorization configuration
- Log in to ADManager Plus and navigate to Directory/Application Settings.
- Go to Application Integrations, then search for and select Miro.
- Toggle the Enable Miro Integration button on.
- On the Miro Configuration page, click Authorization.
- Perform the steps to generate a client_id and client_secret from Miro, and paste them in the respective value fields.
- Click Configure.
Inbound webhook configuration
Inbound webhooks enable you to fetch user data from Miro and send it to ADManager Plus. The attribute mapping configured in this section can be selected as the data source during automation configuration. To configure an inbound webhook for Miro:
- Under Inbound Webhook, click Miro Endpoint Configuration.
- In the Endpoint Configuration tab, an endpoint, Miro USERS ENDPOINT, comes preconfigured. However, if you would like to use a new endpoint to import users, you can configure one using the + Add API endpoint button and filling in the required fields as per Miro's API documentation. Click here to learn how.
- The API key value pair is preconfigured as a header for authenticating API requests as configured during authorization configuration.
- Macros: You can add macros to your endpoint configuration to dynamically change it as per your requirement using the macro chooser component
- Refer to Miro's API documentation and configure additional headers and parameters, if required. In the Settings tab, the Repeat calling this endpoint option will be configured to fetch 30 records per call. This will be repeated until no next page token is received.
- Once done, click Test & Save. A response window will display all the requested parameters that can be fetched using the API call. After verifying if the requested parameters have been called to action, click Proceed.
- Refer to Miro's API documentation to learn about the parameters that must be configured to fetch only specific parameters.
- You can configure multiple endpoints for Miro using the + Add API endpoint button. Click here to learn how.
- Click Data Source - LDAP Attribute Mapping to match endpoints and to map AD LDAP attributes with the respective attributes in Miro.
- Click + Add New Configuration and perform the following actions:
- Enter the Configuration Name and Description, and select the Automation Category from the drop-down menu.
- In the Select Endpoint field, select the desired endpoint and a Primary Key that is unique to a user (e.g., employeeIdentifier). Note: When multiple endpoints are configured, this attribute must hold the same value in all the endpoints.
- In the Attribute Mapping field, select the attribute from the LDAP Attribute Name drop-down menu and map it with the respective attribute in Miro. If you would like to create a new custom format for this, click Add New Format.
- Click Save.
Note:
Outbound webhook configuration
Outbound webhooks enable you to send changes made in AD to Miro, fetch data from Miro, and carry out tasks in Miro—all from ADManager Plus. The webhooks configured in this section can be included in Orchestration Templates, which in turn can be used during event-driven and scheduled automations. They can also be applied directly on desired users to perform a sequence of actions on them (Management > Advanced Management > Orchestration). To configure outbound webhooks for Miro:
- Under Outbound Webhook, click Miro Webhook Configuration.
- Click + Add Webhook.
- Enter a name and description for this webhook.
- Decide on the action that has to be performed and refer to Miro's API documentation for the API details, such as URL, headers, and parameters.
- Select the HTTP method that will enable you to perform the desired action on the endpoint from the drop-down menu.
- Enter the endpoint URL.
- Configure the Headers, Parameters, and Message Type in the appropriate format based on the API call that you would like to perform.
- Click Test and Save.
- A pop-up window will then display a list of AD users and groups to test the configured API call. Select the desired user or group over which this API request has to be tested and click OK. This will make a real-time call to the endpoint URL, and the selected objects will be modified as per the configuration.
- The webhook response and request details will then be displayed. Verify them for the expected API behavior and click Save.
