Developers
Build on iService
Reference material for the developer and integration surfaces of iService: custom forms, the External APIs settings, webhooks, automation, and published code examples.
Custom forms
iService forms are built with the Forms Wizard and collect visitor data directly into an iService workflow. A form can be embedded in a page with an iframe, so iService owns validation, spam control, and the response, or its fields can be posted to the workflow from your own markup when you want full control of the styling.
The iService Forms developer guide covers the Forms Wizard, field syntax, and the values you can include in agent responses and custom pages.
Workflow API
Each tenant exposes a Workflow API endpoint for programmatic submissions. A request is an
HTTP POST with a JSON body of field-and-value pairs sent to the tenant's
webapp-api endpoint with Content-Type: application/json.
There are two kinds of form. A customer submit form is submitted anonymously, so it is
safe to post from a public web page or embed with an iframe. An agent form acts on behalf
of a signed-in agent, so it authenticates with an iService agent login supplied as request
fields. Both include the routing fields that bind the payload to a workflow, and on
success the response returns a results object, such as the identifier of the created
ticket or account, with
errors and errorDetails arrays for any problems.
Keep agent credentials server-side. Only agent forms require a login. Call those from a trusted back-end service and never place an iService login name or password in browser or other client-side code. Public website forms use anonymous customer submit forms, either posted directly or embedded with the hosted form.
External APIs and integrations
Third-party integrations are configured on the External APIs settings page. iService connects to identity providers for single sign-on (Okta, Microsoft, and Google), Microsoft Graph for Microsoft 365 email, the Heartland payment gateway, OpenAI for AI features, Google Calendar, Salesforce, and Calabrio for workforce management.
Automation and data exchange
Beyond direct APIs, iService exchanges data through automation. Workflow filters can run a webhook when an interaction matches a condition, the Zapier integration connects iService to thousands of applications without code, and the batch utilities and forms import and export contacts and interactions in bulk.
Code examples
Published code examples for the iService application show working form definitions and integration patterns you can adapt for your own tenant.