Integration
Connect Geekbot to SigningHub
When New Report fires in Geekbot, your agent runs Add Document in SigningHub. Describe the whole flow 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 Geekbot and SigningHub to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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 Geekbot can start in SigningHub
When New Report in Geekbot
then Add Document in SigningHub
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 Geekbot and SigningHub
Triggers and actions 1 trigger · 28 actions
- New Report
Triggers when a new standup report is submitted in Geekbot.
- Add out-of-office period
Schedules an out-of-office period for you or, if you are an admin, for another team member, covering whole days from the start date to the end date.
- Add poll
Creates a one-shot Geekbot poll that posts a question with answer choices to a channel.
- Add standup
Creates a new Geekbot standup with its questions, schedule and broadcast channel.
- Delete report
Deletes a standup report you authored, removing its broadcast message if one was posted.
- Delete standup
Deletes a standup and returns the details of the standup that was removed. You must have permission to edit the standup.
- Get current user
Returns the user who owns the connected API key, along with the team they belong to.
- Get poll
Returns one poll you created, including its schedule, channel, members and optionally its questions.
- Get report
Returns one submitted standup report, including who posted it, when, and the answer to each question.
- Get standup
Returns one standup by id, including its schedule, members, broadcast settings and optionally its questions.
- List out-of-office periods
Returns out-of-office periods for the team members you can view, ordered by start date, optionally narrowed by users, standups or a date window.
- List polls
Returns the active and paused polls you created in Geekbot, optionally filtered by state, channel, anonymity or creation date.
- List poll votes
Returns the vote results for a poll, grouped by broadcast and question. Without a date range it covers only the latest broadcast.
- List reports
Returns submitted Geekbot standup reports within a time window, optionally filtered by standup or user.
- List standups
Returns the active and paused standups visible to the connected user, with optional filters for state, anonymity, channel and creation date.
- List teams
Returns the Geekbot team tied to the connected API key, including its users who take part in at least one standup visible to the connected user.
- Start Report
Starts a standup immediately so its report questions go out, either to all of its participants or only to the users or emails you name. Returns the vendor's confirmation that the standup was queued.
- Update standup
Updates a standup's name, schedule, questions, channel and participants. Returns the updated standup.
- Add Digital Signature
Adds a digital signature field to a document in a SigningHub package and assigns it to a recipient in the workflow.
- Add Document
Uploads a document file into an existing SigningHub document package.
- Add Electronic Signature
Adds an electronic signature field to a document in a package, assigned to a recipient in the workflow.
- Add Recipient to Workflow
Adds a signer or other recipient to a document package's workflow.
- Add User
Registers a new user in your SigningHub enterprise account, optionally with a password, role and profile details.
- Create Integration URL
Generates an encrypted SigningHub link that opens a shared document package so a user can view and sign it from your application.
- Create Package
Creates a new document package in SigningHub to hold documents and recipients for a signing workflow.
- Download Package
Downloads a document package as a Base64-encoded file: a PDF for a single-document package, or a zip of all its documents.
- Get Document Fields
Returns the fields on a document in a SigningHub package: signature, initials, in-person, text, checkbox, radio, dropdown, listbox, QR code, attachment and comment fields.
- Get Package
Returns the details of a SigningHub document package: its name, owner, status and the documents it contains.
- Share Document for Signing
Shares a prepared document package with its signers and starts the signing workflow.
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 Geekbot
Geekbot to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Geekbot to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Geekbot to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Geekbot to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Geekbot to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Geekbot to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into SigningHub
Questions
Geekbot and SigningHub, answered
What can start an automation from Geekbot?
Any of Geekbot's 1 trigger in the catalog, including New Report. Describe the moment in plain language and your agent picks the right one.
What can your agent do in SigningHub when something happens in Geekbot?
Any of SigningHub's 11 actions, including Create Integration URL, Create Package, Add Digital Signature and Add Document. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SigningHub to Geekbot?
SigningHub has no triggers in the catalog today, so automations start in Geekbot. If you need the other direction, ask: your agent reads SigningHub's API documentation and adds it.
Do I have to build a connector for Geekbot or SigningHub?
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.
Can my AI client use Geekbot and SigningHub without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.