Discovery connector input nodes
You can use the discovery connector input nodes to monitor an application endpoint for events and receive input when a specified event occurs.
When new events occur in the endpoint application, they trigger the input node to perform the actions that have been configured on the node. An event can be considered as a change or an activity that occurs in an application, such as a contact being created in Salesforce. An action is an operation that IBM® App Connect Enterprise initiates, such as retrieving contact details from Salesforce so that they can be processed in some way later in the flow. For example, you might want to configure a Salesforce Input node to be triggered every time a new order is created in Salesforce, and to retrieve the details of that order.
App Connect Enterprise supports streamed events and polled events. Some input nodes are configured to receive streamed events from a source application, and others are configured to poll an application for events. A small subset of input nodes, including the Salesforce Input node, use either streaming or polling, depending on the object and action selected.
Streamed events:
Some input nodes support event streaming from source applications. These applications send event notifications in real time to the input node whenever a particular type of change occurs in the application, such as when an object or a record is created or updated. When an input node has been configured for an action that uses event streaming, messages are pushed to the message flow as they occur from the target system.
Polled events:
Some discovery connector input nodes can be triggered by polled events. When an input node has been configured for an interaction that uses polling, it calls the endpoint application at specified intervals to determine whether any new events have been created. If events are found, the node is triggered to perform the actions that have been configured. Messages are retrieved by performing a query using the parameters defined on the Polling tab of the node.
If a polling interaction is selected during connector discovery, you can set polling properties
in the Connector Discovery wizard. The polling interactions are displayed in the wizard when you
click Configure more events. You can edit these properties before saving
them. The Polling interval property on the input node specifies the intervals
between the polls, which check for a change in state. For example, if you set the Polling
interval property on a Salesforce Input node to
2, the node asks Salesforce every two
minutes to check for new or changed data.
- Created timestamp field
- This property specifies the field in the object that contains the creation timestamp that is used to determine which objects are detected by polling and returned by the connector to the input node. Objects created after the specified time are detected and returned to the node.
- Last updated timestamp field
- This property specifies the field in the object that contains the last-updated timestamp that is used to determine which objects are detected by polling and returned by the connector to the input node. Objects updated after the specified time are detected and returned to the node.
- Format of the timestamps
- This property specifies the format of the timestamps in the Created timestamp
field and Last updated timestamp field of the object, using letters.
For example:
YYYY-MM-DDTHH:mm::ssZ.
- Timezone
- This property specifies the time zone that applies to the timestamps. The default time zone is UTC (Coordinated Universal Time).
- Polling interval (minutes)
- This property specifies the polling interval, in minutes, which controls how frequently the node checks for changes to the object.
- Is created timestamp queryable
- This property is applicable only for new events (CREATED_POLLER). If this property is selected, polling uses the Created timestamp field only. If it is not selected, polling uses the Created timestamp field and the Last updated timestamp field.
The timestamp properties are applicable only to specific actions:
- When the action is
CREATEDORUPDATED_POLLER, only the Last updated timestamp field property is used when polling. The Created timestamp field is not used. The poll returns all objects that have been created or updated in that polling interval. - When the action is
UPDATED_POLLER, both the Created timestamp field and Last updated timestamp field properties are used when polling. The poll returns all objects that have been updated in the polling interval, excluding newly created objects. - When the action is
CREATED_POLLER, both the Created timestamp field and Last updated timestamp field properties are used when polling. The poll returns all objects that have been created in the polling interval, excluding those that have been subsequently updated. - When the action is
CREATED_POLLERand the Is created timestamp queryable property is checked, only the Created timestamp field property is used when polling. The Last updated timestamp field property is not used. The poll returns all objects that have been created in the polling interval.
The Action properties are displayed in the Basic tab, and polling actions
are indicated by the suffix _POLLER. App Connect Enterprise polls the application
at the intervals that you have specified, and if an update has a timestamp after the time when the
flow was started, the flow is triggered and the actions in the flow are completed. In order for this
to happen, the endpoint application must filter by timestamp, so that it can retrieve all objects
that have been created or changed since a specified time.
For information about the discovery connector request nodes that are provided by IBM App Connect Enterprise, see Discovery connector request nodes. For more information about discovery connector nodes, see Discovery connector nodes.
The following discovery connector input nodes are provided with IBM App Connect Enterprise:
- Apptio Targetprocess Input node
-
Use the Apptio Targetprocess Input node in a message flow to monitor and accept input from Apptio Targetprocess.
- Asana Input node
-
Use the Asana Input node to monitor and receive input from Asana.
- Businessmap Input node
-
Use the Businessmap Input node to monitor and accept input from Businessmap.
- ClickSend Input node
-
Use the ClickSend Input node in a message flow to monitor and accept input from ClickSend.
- CMIS Input node
-
Use the CMIS Input node to monitor and receive input from CMIS.
- Coupa Input node
-
Use the Coupa Input node to monitor and receive input from Coupa.
- Eventbrite Input node
-
Use the Eventbrite Input node to monitor and receive input from Eventbrite.
- Front Input node
-
Use the Front Input node in a message flow to monitor and accept input from Front.
- GitHub Input node
-
Use the GitHub Input node in a message flow to monitor and receive input from GitHub.
- GitLab Input node
-
Use the GitLab Input node to monitor and receive input from GitLab.
- Gmail Input node
-
Use the Gmail Input node to monitor and receive input from Gmail.
- Google Calendar Input node
-
Use the Google Calendar Input node to monitor and receive input from Google Calendar.
- Google Cloud PubSub Input node
-
Use the Google Cloud PubSub Input node in a message flow to monitor and receive input from Google Cloud Pub/Sub.
- Google Sheets Input node
-
Use the Google Sheets Input node to monitor and receive input from Google Sheets.
- Greenhouse Input node
-
Use the Greenhouse Input node in a message flow to monitor and accept input from Greenhouse.
- IBM Engineering Workflow Management Input node
-
Use the IBM Engineering Workflow Management Input node to monitor and receive input from IBM Engineering Workflow Management.
- IBM Maximo Input node
-
Use the IBM Maximo Input node in a message flow to monitor and receive input from IBM Maximo.
- IBM OpenPages with Watson Input node
-
Use the IBM OpenPages with Watson Input node to monitor and receive input from IBM OpenPages with Watson.
- Insightly Input node
-
Use the Insightly Input node to monitor and receive input from Insightly.
- Jira Input node
-
Use the Jira Input node in a message flow to monitor and receive input from Jira.
- LDAP Input node
-
Use the LDAP Input node to monitor and receive input from LDAP.
- Magento Input node
-
Use the Magento Input node to monitor and receive input from Magento.
- MailChimp Input node
-
Use the MailChimp Input node to monitor and receive input from MailChimp.
- Marketo Input node
-
Use the Marketo Input node to monitor and receive input from Marketo.
- Microsoft Active Directory Input node
-
Use the Microsoft Active Directory Input node to monitor and receive input from Microsoft Active Directory.
- Microsoft Dynamics 365 for Sales Input node
-
Use the Microsoft Dynamics 365 for Sales Input node to monitor and receive input from Microsoft Dynamics 365 for Sales.
- Microsoft Entra ID Input node
-
Use the Microsoft Entra ID Input node to monitor and receive input from Microsoft Entra ID.
- Microsoft Excel Online Input node
-
Use the Microsoft Excel Online Input node to monitor and receive input from Microsoft Excel Online.
- Microsoft Exchange Input node
-
Use the Microsoft Exchange Input node to monitor and receive input from Microsoft Exchange.
- Microsoft SharePoint Input node
-
Use the Microsoft SharePoint Input node to monitor and receive input from Microsoft SharePoint.
- Microsoft Teams Input node
-
Use the Microsoft Teams Input node to monitor and receive input from Microsoft Teams.
- Microsoft Viva Engage Input node
-
Use the Microsoft Viva Engage Input node to monitor and receive input from Microsoft Viva Engage.
- monday.com Input node
-
Use the monday.com Input node in a message flow to monitor and receive input from monday.com.
- Oracle Human Capital Management Input node
-
Use the Oracle Human Capital Management Input node to monitor and receive input from Oracle Human Capital Management.
- Salesforce Commerce Cloud Digital Data Input
-
Use the Salesforce Commerce Cloud Digital Data Input node to monitor and receive input from Salesforce Commerce Cloud Digital Data.
- Salesforce Input node
-
Use the Salesforce Input node to monitor and receive input from Salesforce.
- ServiceNow Input node
-
Use the ServiceNow Input node to monitor and receive input from ServiceNow.
- Shopify Input node
-
Use the Shopify Input node to monitor and receive input from Shopify.
- Slack Input node
-
Use the Slack Input node to monitor and receive input from Slack.
- SurveyMonkey Input node
-
Use the SurveyMonkey Input node to monitor and receive input from SurveyMonkey.
- Toggl Track Input node
-
Use the Toggl Track Input node in a message flow to monitor and accept input from Toggl Track.
- Wrike Input node
-
Use the Wrike Input node in a message flow to monitor and accept input from Wrike.
- Wufoo Input node
-
Use the Wufoo Input node to monitor and receive input from Wufoo.
- Zendesk Service Input node
-
Use the Zendesk Service Input node to monitor and receive input from Zendesk Service.
- Zoho Books Input node
-
Use the Zoho Books Input node in a message flow to monitor and accept input from Zoho Books.
- Zoho CRM Input node
-
Use the Zoho CRM Input node in a message flow to monitor and accept input from Zoho CRM.
- Zoho Recruit Input node
-
Use the Zoho Recruit Input node in a message flow to monitor and accept input from Zoho Recruit.