ION Factory OS
  • Welcome to ION
  • Features
    • Procedures
      • Steps
        • Content
        • Datagrid
        • Fields
        • Attributes
      • Dependencies
      • Part-Procedure Relationship
      • Attributes
      • Standard Steps
      • Installation Requirements (Beta)
      • Nested Steps and Nested Standard Steps
      • Procedure Best Practices
    • Runs
      • Run Execution Overview
      • Runs And Step States
      • Batching Runs
        • Batching 2.0 Changes
      • Workcenter execution
      • Split Inventory on a Run
      • Redlines
      • Export run data
      • Scheduling runs
      • Time Tracking
      • Attributes
      • Outside Processing
      • Runs Best Practices
    • Parts Library
      • As-built Bill of Materials (aBOM)
        • Editing aBOM build requirements
        • aBOM Beta Changes
          • aBOM actions for developers
      • Inventory
        • Inventory status
        • Inventory splitting
        • Inventory merging
        • Inventory scrapping
        • Kitting
        • Inventory Movement Automations
      • Manufacturing bill of materials (mBOM)
        • mBOM versions
        • Made on Assembly (MOA)
        • Part Substitutes
        • Reference designators
      • Part Attributes
      • Part revision interchangeability
      • Supplier Part Numbers & Purchase Unit Conversions
    • Kitting and Inventory Fulfilment
      • Kit Statuses and Workflows
      • Inventory requests
      • Kitting and runs
      • Fulfilling Multiple Kits
      • Kanban Kitting
    • Purchasing
      • Purchase Orders
        • Types of Purchases
        • Purchase Order Approvals
        • Purchase Order FAQs
        • Supplier Part Numbers & Unit Conversions
        • PO Requirements, Terms, and Quality Clauses
      • Receiving/Inspection
      • Outside Processing
      • Consigned Parts
    • Barcode Labels
      • Templating
        • ION barcode minimum sizes
        • Sample templates
      • Printing
        • Configuring Zebra Browser Print
        • Server Based Barcode Printing (PrintNode)
      • Scanning
        • Scan barcodes from other systems
    • Quality
      • Issues
      • Further Actions - CAPA
      • Issues States, Dispositions, and Resolutions
      • Quality Best Practices
    • Tools
    • Locations
    • Attributes
    • Labels
      • Deleting labels
    • Notifications
    • Search
    • Settings
      • Role based access control
        • Full Glossary of ION Permissions
    • ION Actions
      • ION Actions examples for Quality
      • ION Actions examples for Runs and Procedures
      • ION ACTIONS examples for Supply Chain
  • Analytics
    • Inventory valuation
    • Part impact analysis
    • Users, Roles, Teams
    • Analytics FAQ
    • Data Connector
    • Data Products
  • Plans and Autoplan
    • Autoplan
    • Autoplan glossary
    • Preparing to use Autoplan
    • Clear to build reporting
    • Running Autoplan on a schedule
    • Firm and blocked plan items
    • Location constraints
    • Autoplan suggested suppliers and procedures
    • Reorder point
    • Plan input serial numbers
    • Applying a calendar
    • Plan Reservations
    • Independent schedules
    • Drive demand from kits
    • Drive demand below buy parts configuration
    • Group plan items with the same date
    • Manualy Changing Autoplan Status
  • API
    • How to create an App with ION
    • Access Tokens
    • About GraphQL
    • Interactive API explorer
    • API Keys
    • Examples
      • Notifications
      • Runs
      • Automatically updating fields in runs
      • Parts and Part Revisioning
      • mBOMs
      • Part Inventory and Kitting
      • aBOM (As-built Bill of Materials)
      • Edit time-tracking session data
    • Changelog
    • Webhooks
    • Pagination
  • Automations
    • Auto-checkout of Run Steps
    • Auto-Consumption of Lineside Inventory
    • Automatically Send Purchases to Suppliers
    • Set Close by Run Step on Issue Creation
    • Intent Management / Grade / Tier / Pedigree
      • Data Imprinting
      • ION Actions for Intent
    • Auto-Update mBOM Revision on Part Revision Update
    • Auto-approve part-procedure relationships
    • Purchase Order PDF and Versions
    • Auto Populate PO Line Attributes
    • Imprint Attributes from One Object to Another on a Desired Event
  • Integrations
    • Deploying Integrations and Automations
    • Arena
    • Cofactr
    • Datum
    • Duro
    • NetSuite
      • Purchasing in NetSuite, Receiving in ION
      • Work Order/Assembly Builds
    • Procurable
    • PDF Generator
    • Quickbooks
    • Ramp
    • Silkline Integration
    • Slack
    • Smartsheet
    • SOLIDWORKS
    • Teamcenter
  • Training
    • Standard Operating Procedures
      • Cycle Counting
      • Tool Utilization
    • Guided Flows
    • ION Sandbox
    • Chat Support for ION
  • Troubleshooting
    • Resetting your password
    • Resetting your Multi-Factor Authentication
    • You have no roles... error
  • Changelog
  • Adminstration
    • Security
      • Backups and Security FAQ
      • Single Sign-On (SSO)
        • Okta SAML connection setup
      • Export Control
      • Report Generator Disclaimer
    • Browser and Device Compatibility
    • Authentication
      • My company is new to ION, logging in for the first time.
      • I'm told I'm not authorized to access the application
      • My account has been deactivated
    • Login Page
  • Tickets Portal
Powered by GitBook
On this page
  • Steps
  • Troubleshooting

Was this helpful?

  1. Integrations

Deploying Integrations and Automations

This page outlines the steps to successfully deploy both integrations and automations within ions Integrations page.

PreviousIntegrationsNextArena

Last updated 2 months ago

Was this helpful?

For troubleshooting click here Troubleshooting

Steps

Step 1: Navigate to our

  • Search for the integration / automation you'd like to deploy and click Configure.

  • Scroll to see all the available integrations and automations that are currently available.

  • NOTE: This list is ever expanding so check back often to see what new has been added!

Step 2: Configure ion-api Connection

  • Input your API keys into the following boxes and select your environment

  • NOTE: The API keys generated in your staging environment will not have the correct endpoints for that instance of the integration or automation to work in your production environment.

Step 3.0: Other Fields

  • Often times an integration or automation needs additional parameters setup to point at desired objects or actions.

  • The sub-steps below will provide examples of how those types of fields are filled out and more documentation is available on an integration by integration basis for what those fields mean in their specific use case.

Step 3.1: Setup Free Text Custom Fields

  • Many of our automations contain custom fields that need to be setup. These are often times pointing towards a specific ION object you want to listen to, mutate or create.

  • Most of the time these types of free text input fields will correspond to a custom attribute that is within your Org. Settings.

Step 3.2: Setup Pick-list Custom Fields

  • Sometimes input fields will be a pre-defined list that the user can choose from during setup. In this case there will be a description below the input box that will inform the user what this selection will have an affect on.

Step 3.3: Setup Webhook Related Triggers

  • Less common, a third type of selection one might have to make is defining what types of trigger you want to initiate the automation. This will not be an option on every integration/automation.

  • Two very relevant terms on the webhooks page, WebhookSubscriptionActions and ResourceEnum whcih you can explore more IONs GraphiQL interface documentation explorer.

  • In practice putting webhook related information into an automation may look like the below, where you define the ResourceEnum (what you are listening to) and the WebhookSubscriptionActions (what you are listening for).

  • NOTE: Input format matters here, it should be representative of how it is displayed in the GraphQL documentation explorer.

  • Webhooks are setup when instances of an integration or automation are first instantiated and are only deactivated when instances of an integration or automation are deactivated, not paused.

Step 4.0: Setup of External Software Integration Connections (Email, Finance, PLM, QMS, MRP)

  • If you are setting up an integration you are likely interfacing with another software such as Arena, Duro or Smartsheet to name just a few of our current partnerships.

  • These platforms will have different ways of configuring their respective connections and you will follow steps specific to those integrations using instructions elsewhere in this manual.

Troubleshooting

Common Issue 1:

  • Symptom: Not able to see the integrations page.

  • Cause: You're organization hasn't deployed any integrations or automations before.

  • Solution: Reach out to First Resonance and request access to the ION Marketplace. Once permissions are granted spend some time exploring how you can maximize your manufacturing operations!

Common Issue 2:

  • Symptom: Automation is not triggering desired result.

  • Cause: You've recently tried to deploy in another environment or switch the environment you are pointing to.

  • Solution:

    If you are trying to spin up a new instance in a new environment you need to make sure that you are using unique API keys from those respective environments for those specific deployments. A sandbox API key and secret will NOT work in the prod environment. If you find that is what happened I would recommend the following steps, it’s a few extra steps but should cleanup any crossed wires.

    1. Record the current setup of your instances so you can easily recall them.

    2. Deactivate your instances to get rid of any stray, interconnected webhook subscriptions / receivers between your two environments.

    3. Create two new instances making sure to use those unique API Keys and Secrets for your respective environments.

    4. Double check your triggers if applicable when creating the instance to make sure you’re looking at the correct resource and action.

Common Issue 3:

  • Symptom: You have successfully deployed the integration, but are seeing no executions from the integration. When you look at the webhook events in the ION API, you see 401 errors.

  • Cause: You have populated the details of the trigger for the integration with API keys.

  • Solution: Go to the summary page on an integration you have deployed and hit reconfigure. From there, expand the trigger details section. Anywhere you have listed an API key here needs to be deleted by hitting the trash can icon next to the API key! See below for what the trigger details should look like, with nothing below the URL for each flow.

Refer to the documentation for information on how to get your API keys

NOTE: API Keys inherit the permissions of the user at the time of the being created. Here are the instructions on creating a new and then you can

The example below is from the automation where the customer has the ability to choose what attributes they would like to imprint on the selected imprint objects.

See the page, , to understand more about how these work along with the resources available to determine the entire suite of webhook subscriptions available.

API key
API Key
API key
plug that into the automation.
Data Imprinting
Webhooks
integrations page
Integrations button in bottom left of ION
ION API Connection Setup
Input text fields to match the custom attributes the user wants to imprint from one object to another.
Exampe of selection box style automation setup.
GraphQL Explorer in Bottom Left of ION
Documentation Explorer top Right of GraphQL API Screen
ResourceEnum shown in the Key field and WebhookSubscriptionActions shown in the Value field
Notice that no API keys have been added to the trigger section!