Integration
Connect Float to Signatureapi
When something happens in Float, your agent does the next thing in Signatureapi. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Float and Signatureapi to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Float can start in Signatureapi
When New Allocation in Float
then Add ceremony in Signatureapi
When New Client in Float
then Add deliverable in Signatureapi
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Float and Signatureapi
Triggers and actions 15 triggers · 36 actions
Trigger
New AllocationTriggers when a new allocation is created.
Trigger
New ClientTriggers when a new client is added.
Trigger
New DepartmentTriggers when a new department is added.
Trigger
New Logged TimeTriggers when a new logged time is created.
Trigger
New MilestoneTriggers when a new milestone is created.
Trigger
New PersonTriggers when a new person is added.
Trigger
New PhaseTriggers when a new phase is created.
Trigger
New ProjectTriggers when a new project is created.
Trigger
New Project TaskTriggers when a new project task is created.
Trigger
New Time OffTriggers when a new time off is created.
Trigger
Updated AllocationTriggers when an allocation is modified.
Trigger
Updated Logged TimeTriggers when a logged time is modified.
Trigger
Updated PhaseTriggers when a phase is modified.
Trigger
Updated ProjectTriggers when a project is modified.
Trigger
Updated Project TaskTriggers when a project task is modified.
Action
Create AllocationCreates a new allocation.
Action
Create ClientCreates a new client.
Action
Create DepartmentCreates a new department.
Action
Create Logged TimeCreates a new logged time.
Action
Create MilestoneCreates a new milestone.
Action
Create PersonCreates a new person.
Action
Create PhaseCreates a new phase.
Action
Create ProjectCreates a new project.
Action
Create Project TaskCreates a new project task.
Action
Create Time OffCreates a new time off.
Action
Find AllocationFinds an allocation by ID.
Action
Find Logged TimeFinds a logged time by ID.
Action
Find PersonFinds a person by ID, email, or tag(s).
Action
Find ProjectFinds a project by ID, project_code, or tag(s).
Action
Update AllocationUpdate an existing allocation by ID.
Action
Update Logged TimeUpdate an existing logged time entry by ID.
Action
Update MilestoneUpdate an existing milestone by ID.
Action
Update PersonUpdate an existing person by ID.
Action
Update PhaseUpdate an existing phase by ID.
Action
Update ProjectUpdate an existing project by ID.
Action
Update Project TaskUpdate an existing project task by ID.
Action
Add ceremonyCreates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.
Action
Add deliverableCreates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.
Action
Add envelopeCreates an envelope with documents and recipients and starts the signing process.
Action
Add uploadUploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.
Action
Cancel envelopeCancel an in-progress envelope so remaining recipients can no longer sign.
Action
Delete envelopeDelete an envelope.
Action
Get deliverableRetrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.
Action
Get envelopeRetrieve a single envelope by id.
Action
Get recipientRetrieves a recipient's details, including status, ceremony information and completion timestamp.
Action
Get uploadFetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.
Action
List deliverablesReturns the deliverables (signed PDFs with audit log) of an envelope, earliest first.
Action
List envelopesLists envelopes in the account, most recent first, optionally filtered by status or topic.
Action
Resend requestResends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.
Action
Update envelopeUpdate mutable fields (e.g. title, metadata) of an existing envelope.
Action
Update recipientReplaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Float
Float to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Float to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Float to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Float to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Float to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Float to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
More into Signatureapi
HubSpot to SignatureapiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SignatureapiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to SignatureapiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to SignatureapiGoogle Sheets
Gmail to SignatureapiGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SignatureapiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Float and Signatureapi, answered
What can start an automation from Float?
Any of Float's 15 triggers in the catalog, including New Allocation, New Client, New Department and New Logged Time. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Signatureapi when something happens in Float?
Any of Signatureapi's 15 actions, including Update envelope, Update recipient, Add ceremony and Add deliverable. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Signatureapi to Float?
Signatureapi has no triggers in the catalog today, so automations start in Float. If you need the other direction, ask: your agent reads Signatureapi's API documentation and adds it.
Do I have to build a connector for Float or Signatureapi?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.