Browse categories
Explore
Fiverr Pro
English
$
USD
I will build or fix ai workflows and rest API integrations
Xiao Bai
About this gig
Connect AI to a useful business workflow, with a clear scope and reviewable actions.
I build or fix small, code-based integrations between one supported AI provider and your authorized REST API. A typical project turns one inbound lead payload into structured categories and a reply draft, with CRM lookup or a human-approved CRM update depending on the package.
You receive source code, setup notes, agreed automated tests, and a local test walkthrough. Tool access is allowlisted, requests are bounded, and writes require explicit approval. Reply drafts are not sent automatically.
My self-initiated lead workflow demo passed 28 automated tests using real local HTTP requests, a simulated classifier and a mock CRM. It is not a live LLM or customer deployment.
Please message me before ordering with your workflow, API documentation, and sample data with sensitive details removed. Provider compatibility is confirmed first. API usage fees, deployment, hosting, production security hardening, and ongoing operation are separate. Never send passwords or API keys in chat.
Get to know Xiao Bai
Xiao Bai
Backend and AI Agent Developer, Java, Go and API Integrations
- FromChina
- Member sinceOct 2026
- Avg. response time1 hour
Languages
Chinese, English
I develop backend services and REST APIs with Java, Spring Boot and Go, including bug fixes, database queries, Redis caching and Docker deployment. I also build AI agent workflows that connect language models to business APIs, with tool calling, human approval for sensitive actions and audit logs. I focus on clear requirements, maintainable code, testing and handover documentation. Communication is primarily written. AI-assisted development includes code review and testing; model and hosting costs are scoped separately.
FAQ
What is included in each package?
Basic fixes one reproducible defect in a runnable AI/API integration. Standard adds one input schema, AI categorization, one CRM read endpoint and an unsent draft. Premium adds one human-approved CRM write. Source, setup notes and 6/10/16 agreed tests are included.
Will replies or CRM changes happen automatically?
Replies remain drafts. Standard is read-only. Premium adds one CRM create OR update action behind a separate local human-approval step. The model cannot approve its own proposal. Uncertain write outcomes stop for review, not automatic retry.
What API access and costs are required?
You provide one authorized business API, documentation, test data, and your own AI provider account and credits. Compatibility is checked before ordering. Model/API fees, subscriptions, hosting, deployment, maintenance and production hardening are excluded.
Is this an n8n or production service?
No. This is code-based integration in one agreed language: Python, Java or Go. Packages deliver a small local test prototype or scoped fix, not a production autonomous system. No n8n experience, automatic outreach or live customer deployment is claimed.
How should I share credentials?
Never paste passwords, API keys, access tokens or private customer data into chat. Use synthetic/redacted samples. Configure authorized, least-privilege test credentials using environment variables or your secret manager; source examples contain placeholders only.
What does the portfolio demo prove?
My self-initiated lead workflow demo passed 28 automated tests using real local HTTP requests, a simulated classifier and a mock CRM. It demonstrates bounded calls, human-approved writes and unsent reply drafts. It is not a live LLM, n8n project or customer deployment.
What are the scope and acceptance limits?
One workflow, input schema, provider/model, language and authorized API. Standard: one read endpoint/tool. Premium: one read plus one write endpoint, two tools. Agree outputs and test cases first. Tests use fixtures/mocks or authorized test APIs; live checks are labelled separately.
What counts as a revision?
A consolidated review round within the agreed workflow and acceptance criteria. New providers, endpoints, tools, business rules, workflows, platform connectors or UI require new scope. Corrections needed to meet the agreed acceptance criteria are not sold as extra features.
