4me
Auto Mate and 4me Guide
Introduction
Explore the integration between Auto Mate and 4me, detailing the available actions in Auto Mate for interacting with 4me functionalities.
This document delves into the seamless integration between Auto Mate, a powerful workflow automation platform, and 4me, an advanced IT service management (ITSM) solution. It provides insights into the actions within Auto Mate that empower users to interact with the diverse functionalities offered by 4me.
What is 4me?
4me is a robust ITSM product designed to optimize service delivery for organizations, government agencies, and managed service providers (MSPs). It offers an extensive suite of functionalities to streamline IT service management processes, including:
Incident Management: Processes to identify, diagnose, and resolve unexpected interruptions to IT services.
Request Fulfillment: Managing service requests from users, covering creation, approval, fulfillment, and closure.
Change Management: Planning, implementing, and reviewing changes to IT infrastructure and services.
Asset Management: Tracking and managing IT assets throughout their lifecycle, including hardware, software, and licenses.
Auto Mate Integration with 4me
Auto Mate offers a seamless integration with 4me through a collection of pre-built actions. These actions empower users to Auto Mate various tasks within their workflows by harnessing the capabilities of 4me. Some examples include:
Automatically creating service requests in 4me upon receiving emails from customers.
Updating configuration item statuses in 4me based on predefined criteria.
Adding notes to existing requests within 4me workflows.
Using the Integration
Instructions on how to utilize the actions available in the Auto Mate -4me integration.
Credentials
Steps to establish a secure connection between Auto Mate and 4me using credentials.
How to Create Credentials: To utilize the actions within Auto Mate , you need to establish a credential that connects to your 4me account/instance. This credential acts as a secure bridge, enabling Auto Mate to interact seamlessly with your 4me data. You can add your credentials at Vault page.
How To Use Actions
Detailed instructions on using specific actions available in the Auto Mate -4me integration.
4me Markdown text to HTML
Description: Convert text written in 4me's markdown syntax to HTML format.
Purpose: This action enables the conversion of markdown-formatted text into HTML for display or processing.
Usage:
Provide the desired markdown text in the input field.
Run the action to generate the HTML-converted output.
Inputs:
4me Markdown Text: The text written in 4me's markdown syntax.
Outputs:
HTML Output: The HTML-converted output of the provided markdown text.
Add Note
Description: Add a note to a specific request within 4me.
Purpose: Facilitates the addition of notes to requests for documentation or communication purposes.
Usage:
Enter the unique identifier of the request.
Input the content of the note.
Execute the action to add the note to the specified request.
Inputs:
Request ID: The unique identifier of the request to which the note will be added.
Note Text: The text content of the note.
Outputs:
Note Added: Information about the successful addition of the note.
Add Note with Markdown
Description: Add a note with markdown content to a specific request within 4me.
Purpose: Allows for the addition of formatted notes with attachments to requests.
Usage:
Provide references to any stored files to be attached with the note.
Enter the note content in 4me's markdown syntax.
Specify the unique identifier of the request.
Execute the action to add the formatted note to the request.
Inputs:
Storage Files: References to files stored that need to be attached with the note.
4me Markdown Note: The note content in 4me markdown syntax.
Request ID: The unique identifier of the request to add the note.
Outputs:
Note Added: Confirmation or details of the note added with markdown content.
Assign Request
Description: Assign a request to a specific individual or group within 4me.
Purpose: Streamlines the process of assigning tasks or requests to responsible parties.
Usage:
Provide the unique identifier of the request to be assigned.
Specify the desired recipient or group for assignment.
Execute the action to assign the request.
Inputs:
request_id: The unique identifier of the request to be assigned.
Outputs:
4me_resp: The response or result of the assignment operation.
Create a Site
Description: Create a new site within the 4me platform.
Purpose: Enables the addition of new physical or virtual locations to the system.
Usage:
Enter the name of the site to be created.
Execute the action to generate the new site.
Inputs:
Name: The name of the site to be created.
Outputs:
Site Details: Details of the newly created site.
Create an Organization
Description: Create a new organization entity within 4me.
Purpose: Facilitates the addition of new organizational units or entities.
Usage:
Input the name of the organization to be created.
Execute the action to create the new organization.
Inputs:
Name: The name of the organization to be created.
Outputs:
Organization Details: Details of the newly created organization.
Create Configuration Item
Description: Create a new configuration item within 4me.
Purpose: Allows for the addition of new items to the configuration management database.
Usage:
Specify the product associated with the configuration item.
Define the current status of the configuration item.
Execute the action to create the new configuration item.
Inputs:
Product: The product associated with the configuration item.
Status: The current status of the configuration item.
Outputs:
4me_resp: The response from the creation process, typically details of the created item.
Create Person
Description: Create a new person record within 4me.
Purpose: Facilitates the addition of new individuals to the system.
Usage:
Enter the primary email address of the person.
Provide the full name of the person.
Execute the action to create the new person record.
Inputs:
Primary Email: The primary email address of the person.
Name: The full name of the person.
Outputs:
4me_resp: The response containing details of the created person.
Create Product
Description: Create a new product entity within 4me.
Purpose: Allows for the addition of new products or services to the system.
Usage:
Specify the model designation of the product.
Define the category to which the product belongs.
Provide the brand and name of the product.
Execute the action to create the new product.
Inputs:
Model: The model designation of the product.
Category: The category to which the product belongs.
Brand: The brand of the product.
Name: The name of the product.
Outputs:
4me_resp: The response including details of the newly created product.
Create Request
Description: Create a new service request within 4me.
Purpose: Enables users to submit new requests for IT services or assistance.
Usage:
Specify the subject or title of the request.
Provide additional notes or descriptions for the request.
Select the category and service instance related to the request.
Define the level of impact the request has.
Execute the action to create the new request.
Inputs:
Subject: The subject or title of the request.
Note: Additional notes or description for the request.
Category: The category under which the request falls.
Service Instance: A reference to the service instance related to the request.
Impact: The level of impact the issue described in the request has.
Outputs:
Request Result: The result or response from creating the request.
Create Service Instance
Description: Create a new instance of a service within 4me.
Purpose: Allows for the addition of new instances or versions of services.
Usage:
Specify the name or identifier of the service.
Provide a name for the new service instance.
Execute the action to create the new service instance.
Inputs:
Service: The name or identifier of the service.
Name: The name given to the service instance.
Outputs:
4me_resp: The response from the system after creating the service instance.
Get Last Note of Request
Description: Retrieve the most recent note added to a specific request within 4me.
Purpose: Allows users to view the latest communication or updates related to a request.
Usage:
Input the unique identifier of the request.
Execute the action to retrieve the last note of the request.
Inputs:
Request ID: The unique identifier of the request.
Outputs:
Last Note: Retrieves the most recent note added to the specified request.
Get Note Attachments
Description: Retrieve any attachments associated with a specific note within 4me.
Purpose: Enables users to access files or documents linked to a note.
Usage:
Input the unique identifier of the note.
Execute the action to retrieve the note attachments.
Inputs:
Note ID: The unique identifier of the note.
Outputs:
Note Attachments: Retrieves any attachments associated with the note.
Get Site with ID
Description: Retrieve information about a specific site within 4me using its unique identifier.
Purpose: Allows users to view detailed information about a particular site.
Usage:
Input the unique identifier for the site.
Execute the action to retrieve site information.
Inputs:
Site ID: The unique identifier for the site.
Outputs:
Site Details: The information of the site retrieved using its ID.
Get Organization with ID
Description: Retrieve information about a specific organization within 4me using its unique identifier.
Purpose: Allows users to view detailed information about a particular organization.
Usage:
Input the unique identifier for the organization.
Execute the action to retrieve organization information.
Inputs:
Organization ID: The unique identifier for the organization.
Outputs:
Organization Details: The information of the organization retrieved using its ID.
Get Configuration Item
Description: Retrieve information about a specific configuration item within 4me using its unique identifier.
Purpose: Allows users to view details and status of a configuration item.
Usage:
Input the unique identifier for the configuration item.
Execute the action to retrieve configuration item information.
Inputs:
CI ID: The unique identifier for the configuration item.
Outputs:
4me_resp: The response from the system after retrieving the configuration item.
HTML to 4me Markdown Formatter
Description: Convert HTML content to 4me-compatible Markdown format.
Purpose: Facilitates the conversion of HTML content for use within 4me.
Usage:
Provide the HTML content to be converted.
Execute the action to generate the 4me Markdown output.
Inputs:
HTML Data: The HTML content to be converted.
Outputs:
4me Markdown Output: The result of converting HTML data into 4me-compatible Markdown format.
List notes of a request
Description: Retrieve all notes associated with a specific request within 4me.
Purpose: Allows users to view a history of communication or updates related to a request.
Usage:
Input the unique identifier of the request.
Execute the action to list all notes of the request.
Inputs:
Request ID: The unique identifier of the request to list notes for.
Outputs:
Request Notes: Retrieves all the notes associated with the specified request.
Update a Site
Description: Update details of an existing site within 4me.
Purpose: Allows users to modify and maintain accurate site information.
Usage:
Input the unique identifier for the site to be updated.
Execute the action to apply updates to the site.
Inputs:
Site ID: The unique identifier for the site you wish to update.
Outputs:
Update Result: The response or result of the update action.
Update an Organization
Description: Update details of an existing organization within 4me.
Purpose: Allows users to modify and maintain accurate organization information.
Usage:
Input the unique identifier for the organization to be updated.
Execute the action to apply updates to the organization.
Inputs:
Organization ID: The unique identifier for the organization you want to update.
Outputs:
Update Result: Results from the update process, showing success or detailing any issues encountered.
Update Configuration Item
Description: Update details of an existing configuration item within 4me.
Purpose: Enables users to modify and manage configuration item information.
Usage:
Input the unique identifier for the configuration item to be updated.
Execute the action to apply updates to the configuration item.
Inputs:
CI ID: Refers to the unique identifier for the configuration item.
Outputs:
4me_resp: The response from the system following the update.
Update Person
Description: Update details of an existing person record within 4me.
Purpose: Allows users to modify and manage individual information.
Usage:
Input the unique identifier or information of the person to be updated.
Execute the action to apply updates to the person record.
Inputs:
People: The unique identifier of the person being updated.
Outputs:
4me_resp: The system's response after attempting the update.
Update Request
Description: Update details of an existing service request within 4me.
Purpose: Enables users to modify and manage service request information.
Usage:
Input the unique identifier of the request to be updated.
Execute the action to apply updates to the request.
Inputs:
Request ID: The unique identifier of the request that needs to be updated.
Outputs:
4me_resp: Provides feedback from the system on the update action.
Update Service
Description: Update details of an existing service within 4me.
Purpose: Allows users to modify and manage service information.
Usage:
Input the unique identifier of the service to be updated.
Execute the action to apply updates to the service.
Inputs:
Services: The unique ID of the service to be updated.
Outputs:
4me_resp: The response from the system post-update.
Update Service Instance
Description: Update details of an existing service instance within 4me.
Purpose: Enables users to modify and manage service instance information.
Usage:
Input the unique identifier of the service instance to be updated.
Execute the action to apply updates to the service instance.
Inputs:
Service Instances: The unique ID of the service instance to be updated.
Outputs:
4me_resp: Feedback from the system on the result of the update operation.
Upload Files to Storage
Description: Upload files or data to the storage within 4me.
Purpose: Allows users to add attachments or documents to requests or notes.
Usage:
Provide the data or contents of the files to be uploaded.
Execute the action to upload the files to the storage.
Inputs:
Attachment Contents: The data or contents of the files to be uploaded.
Outputs:
Uploaded Files: The result of the upload operation.
View Person
Description: Retrieve details of an existing person within 4me.
Purpose: Allows users to view information about individuals in the system.
Usage:
Input the unique identifier or information of the person to be viewed.
Execute the action to retrieve person details.
Inputs:
People: The unique identifier of the person to view.
Outputs:
4me_resp: The system's response containing the requested person's details.
View Request
Description: Retrieve details of an existing service request within 4me.
Purpose: Enables users to view information about specific service requests.
Usage:
Input the unique identifier of the request to be viewed.
Execute the action to retrieve request details.
Inputs:
Services: The unique identifier of the request to view.
Outputs:
4me_resp: Represents the system's response after attempting to view a request.
View Service
Description: Retrieve details of an existing service within 4me.
Purpose: Allows users to view information about services available in the system.
Usage:
Input the unique identifier or information of the service to be viewed.
Execute the action to retrieve service details.
Inputs:
Services: The unique identifier of the service to view.
Outputs:
4me_resp: The output from the system after attempting to view a service.
View Service Instance
Description: Retrieve details of an existing service instance within 4me.
Purpose: Enables users to view information about specific service instances.
Usage:
Input the unique identifier or information of the service instance to be viewed.
Execute the action to retrieve service instance details.
Inputs:
Service Instances: The unique identifier of the service instance to view.
Outputs:
4me_resp: Provides the response from the system after requesting to view a service instance.
Additional Tips
Use Cases
Last updated
