Connectors, API & on-premise reach — found from sitemap — Appian

Cited by

Facts read from this source

• Connector functions purpose Report an error

  “Connector Functions allow developers to build integrations between Appian and other popular enterprise software platforms.”

• Connector usage context Report an error

  “The connectors are available as functions that are intended to be used with interface expressions to build rich record lists and dashboards to present a unified view of data from disparate systems.”

• Connector credentials required Report an error

  “All connectors require credentials to access the target system.”

• Secure credentials store Report an error

  “In order to authenticate with the target system, the connectors retrieve credentials from the secure credentials store.”

• System wide vs per user auth Report an error

  “Each function also takes a usePerUserCredentials parameter, which determines whether the values of system-wide credentials should be used when authenticating with the target system (false) or whether the individual credentials set by the current user should be used (true).”

• System wide credentials location Report an error

  “System-wide credentials are set in the Third-Party Credentials page of the Admin Console.”

• Per user credentials location Report an error

  “Per-user credentials are set by individual users in the Third-Party Credentials settings page.”

• Connector read return type Report an error

  “The connector functions that read from the target system all return the same Dictionary data structure, which contains a field that indicates whether the read was successful and fields that contain the result or error.”

• Connector read error handling Report an error

  “Should an error occur while retrieving data from the target system, the connector function will still return a value instead of throwing an exception that would cause the entire expression to fail to evaluate.”

• Connector writers bind Report an error

  “Connector functions that modify data on the target system are implemented as Writers. Writers can only be used on interfaces and must be used in conjunction with the bind() function.”

• Connector write error handling Report an error

  “If an error occurs when a connector function writes data to an external system, the error will manifest as an expression failure error message in a dialog on the user interface.”

• Connector debug logging Report an error

  “To have this information printed to the application server log file in the <APPIAN_HOME>/logs directory, uncomment the following line in appian_log4j.properties”

• Web service helper functions Report an error

  “a!httpAuthenticationBasic - Creates an object that contains the information required to perform HTTP Basic authentication.”

• Webservicequery write functions Report an error

  “a!wsConfig - Constructs the config parameter to the webservicequery() and webservicewrite() functions.”

• Connector credentials fields Report an error

  “Most connectors require two credentials fields named "Username" and "Password."”

• Connector read data format Report an error

  “The functions request the data in accordance with the target system's API and return the data in the same format as returned by the target system, but transformed into an Appian dictionary.”

• Connector key parameter Report an error

  “The credentials that the connectors use for authentication are identified based on the scsExternalSystemKey parameter present in each connector function.”

• Copyright holder Report an error

  “© 2026 Appian Corporation”

2 facts read from this page are not shown because they could not be confirmed on the page as captured.

Scores citing this record

• The Data Protection Officer Connectors, API & on-premise reach
• The Data Protection Officer European sovereignty
• The Data Protection Officer Connectors, API & on-premise reach
• The Head of IT Connectors, API & on-premise reach
• The Head of IT European sovereignty
• The Head of IT Connectors, API & on-premise reach
• The Integration Engineer Connectors, API & on-premise reach
• The Integration Engineer Connectors, API & on-premise reach
• The Operations Analyst Connectors, API & on-premise reach
• The Operations Analyst Connectors, API & on-premise reach
• The Process Owner Connectors, API & on-premise reach
• The Process Owner Connectors, API & on-premise reach
• The Skeptic Connectors, API & on-premise reach
• The Skeptic Connectors, API & on-premise reach