Development and automation
Give Bob a defined way to work with your own system
The most useful record is often in a system your team built. Bob connects that API to the conversation: the lookup you define, the action you allow, and the result the customer or staff member receives.
Bob connects your own system to the conversation: the lookup you define, the action you allow, and the result the customer or staff member receives.
Start with the business job the API already performs
A customer asks for a job status, an account balance, or a change in your own product. Bob uses the reference the person provides, calls the lookup you configured, and explains the returned result. When the next step writes to your system, Bob prepares the action with the inputs you require and waits for the approval you set. Success, failure, and pending work come back in plain language, so the customer knows what happened and your team can see the exception. The API stays yours. Bob uses only the operations you connect.
Workflows
Look up the record
Retrieve the customer-facing status or account detail the conversation is allowed to use.
Take the approved action
Submit the change with the required fields, validation, and approval, then confirm the result.
Explain the outcome
Tell the customer what succeeded, what is waiting, or what the team needs to finish.
Example workflow
Example workflow
Your system tracks repair jobs. A customer gives the job reference. Bob retrieves the customer-facing status and explains it. If they ask for a change, Bob prepares that request for the staff action you defined instead of exposing the rest of the API.
Illustrative example, not a live execution log.
Connection and setup
Bring the operations, authentication, and example requests you want Bob to use. Store credentials in account setup. Choose which calls are reads and which writes require approval.
How Bob turns a conversation into a useful next step
Bob starts with the customer's request and the business information you approve. When the workflow needs a current record, Bob retrieves it from the connected service. When the next step changes a record or sends a message, Bob follows the permissions and approval steps you configure. The customer gets a useful next response, and your team gets a clear handoff when a person needs to take over.
Questions
Which parts of our API does Bob use?
The lookups and actions you connect. Bob does not browse the rest of the system.
How does a write stay under our control?
You define the inputs, the validation, and the approval step. Bob prepares the action and reports the result.
Who decides what Bob can change or send?
You choose the records Bob reads and the actions he takes. A reply, a record update, or an outbound message follows the approval step you set for that workflow. See the pricing page for plans. This page does not list prices.
Continue this workflow with
These are related workflows, not prerequisites.
Get started with Connect my API
Tell us how your front office handles this job today. You send the message when you are ready.