REST In IntegrationHub Flashcards
What is IntegrationHub?
IntegrationHub is a framework used to interact with third-party platforms in ServiceNow. Developers can use IntegrationHub to build integration actions to execute commands against external platforms.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What are some examples of how to use IntegrationHub?
- Post news to Slack, Teams, or other communication and social media platforms
- Automate onboarding processes to update user information in a Human Resource system, create a user in Active Directory, and assign training to a new employee
- Consume information from and interact with Internet of Things (IoT) devices
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What are steps within the context of IntegrationHub?
Steps are individual actions or operations that are part of an integration flow.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What is an Integration Flow?
A sequence of steps that define the entire integration process. Each step represents a specific actions that should be performed during the integration.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
IntegrationHub provides various pre-built step types that you can use in your integration flows.
Can you list off some of the common step types?
- REST Steps
- SOAP Steps
- Script Steps
- Subflow Steps
- ServiceNow Table Steps
- Utility Steps
———————————————————————
📁 REST in IntegrationHub Developer Documentation
IntegrationHub provides various pre-built step types that you can use in your integration flows.
Can you give a brief description of what a REST Step is?
REST Steps allow you to make HTTP requests to external RESTful APIs.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
IntegrationHub provides various pre-built step types that you can use in your integration flows.
Can you give a brief description of what a SOAP Step is?
Used for interacting with SOAP-based web services
———————————————————————
📁 REST in IntegrationHub Developer Documentation
IntegrationHub provides various pre-built step types that you can use in your integration flows.
Can you give a brief description of what a Script Step is?
These steps enable you to write custom scripts (usually JavaScript) to perform specific actions or transformations.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
IntegrationHub provides various pre-built step types that you can use in your integration flows.
Can you give a brief description of what a Subflow Step is?
You can include other integration flows as subflows within your main flow, allowing for modular and reusable integration designs.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
IntegrationHub provides various pre-built step types that you can use in your integration flows.
Can you give a brief description of what ServiceNow Table Steps are?
These steps are used to interact with ServiceNow tables and records, enabling you to create, update, or retrieve data within your instance.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
IntegrationHub provides various pre-built step types that you can use in your integration flows.
Can you give a brief description of what Utility Steps are?
Utility steps provide various utilities like branching, decision making, or setting variables within the flow.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What benefits does IntegrationHub provide for developers?
- Automates application logic to interact with external platforms
- Enables SMEs (Subject Matter Experts) to develop and share integration actions developers can leverage in custom applications
- Provides natural-language descriptions of integration logic in an application to help non-technical users author flows and understand what flows do.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What is a spoke in the context of IntegrationHub?
A spoke is a logical grouping of related actions, subflows, and supporting application files.
A spoke is a scoped application that includes Flow Designer or IntegrationHub actions or subflows.
Process designers can reuse spoke logic in their own applications.
Their are default included spokes and customers spokes available to download or create.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
How do you create a spoke?
What’s an important thing to remember when creating a spoke here?
You create a spoke in the same way that you would create a scoped application - using studio.
- It’s convention to add the word Spoke to the application name to identify an application as a spoke.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What are the different parts of an endpoint URL?
- Scheme / Protocol
- Domain / Host
- Port
- Path
- Query Parameters
- Fragment Identifier
- Authentication
- HTTP Methods
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What is an Endpoint URL?
A URL by which a REST API is accessed.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What type of data makes up query parameters?
Name:Value Pairs
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What is an inline connection in IntegrationHub and when should it be used / not be used?
An inline connection is a type of connection configuration that allows you to define connection parameters directly within a flow or action, rather than creating a separate connection record in the Connection Registry.
Inline connections are not recommended for production use. Actions should be designed so the action itself does not need to be modified directly to use. Connection and Credentials aliases should be used to connect to REST APIs in production and to separate the configuration from the action definition.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What is a resource path in the context of endpoint URLs?
A resource path is added to the Base URL to create the entirety of the endpoint URL.
An API will include a variety of different resource paths to return different information.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
REST API calls return data in the Response Body.
How is the response body data typically formatted?
It is usually structured in JSON or XML format.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
It is possible to parse a REST API call’s response body into variables that can be used elsewhere in an action or flow.
What is the general strategy to get extracted data from the response?
- Review the response body to select the data to return
- Create input and output variable in the Script step
- — Create an input variable to pass in the Response Body from the REST step.
- — Create output variables to return data from the response
- Create a script to parse and map data
- — Use the JSON.parse() method in a Script step to parse a JSON response body
- — Map the parsed data to the output variables
- Create action outputs for the output variables to make the data available to a flow.
NOTE: To parse XML there is a preincluded XML Parser step.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What are Connection and Credential Aliases?
Pointers to a connection. A connection defines the URL or hostname to connect to a third-party platform.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What is the difference between an inline connection and establishing a connection with Connection and Credential Aliases?
An inline connection creates a connection directly in a REST step, while Connection and Credential Aliases and Connections allows you to define a connection once, then use the connection in any custom action.
———————————————————————
📁 REST in IntegrationHub Developer Documentation
What are some things the Connections and Credential Aliases and Connections Enables?
- Connection details to be configured once for all actions that need to access that connection
- Connection details can be updated without having to reconfigure every action
- Multiple Connection hosts to be managed centrally
———————————————————————
📁 REST in IntegrationHub Developer Documentation