Integration
Connect Gridfox to inFakt
When Record Created fires in Gridfox, your agent runs Find Invoice in inFakt. 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 Gridfox and inFakt 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 Gridfox can start in inFakt
When Record Created in Gridfox
then Find Invoice in inFakt
When Record Created or Updated in Gridfox
then Create Client in inFakt
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 Gridfox and inFakt
Triggers and actions 2 triggers · 21 actions
Trigger
Record CreatedTriggers when a new record is created.
Trigger
Record Created or UpdatedFires when a record in the chosen Gridfox table is created or updated.
Action
Add recordCreate a record in a table.
Action
Add userAdd a user to the project.
Action
Delete recordDelete a record.
Action
Find recordsSearch records in a table by search parameters.
Action
Get recordGet a record by reference field value.
Action
Get record auditGet audit history for a record.
Action
List tablesList tables in the project.
Action
List User Groupslists the project's user groups with their member users (id, email).
Action
Update recordUpdate a record by reference field value.
Action
Add CostAdds a cost to inFakt by uploading a scan or PDF of the cost document (PDF, JPG or PNG, up to 15 MB). The uploaded document appears on the costs list.
Action
Add ProductCreates a product in the inFakt product catalog.
Action
Create ClientCreates a new client in Infakt. Use this to add customers before invoicing or to import clients from external sources (CRM, spreadsheets, etc.).
Action
Delete ClientDeletes a client from your inFakt account.
Action
Find ClientReturns up to 100 inFakt clients matching the given company name, NIP, email or person name.
Action
Find InvoiceReturns the VAT invoices whose number exactly matches the specified invoice number.
Action
Get ClientRetrieves a single inFakt client (kontrahent) by its id, returning the full client record.
Action
Get CostRetrieves a single cost document (cost, document scan or internal evidence) from inFakt by its UUID.
Action
Get ProductRetrieves a single product from your inFakt product catalog by its ID.
Action
List ProductsReturns all products in the inFakt account, optionally filtered by exact product name.
Action
Update ClientUpdates an existing client in inFakt. Only the fields you fill in are changed; blank fields are left as they are.
Action
Update ProductUpdates an existing product in inFakt. Only the fields you fill in are changed; the full updated product is returned.
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 Gridfox
Gridfox to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Gridfox to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Gridfox to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Gridfox to MailchimpMailchimp marketing automation and email platform.
Gridfox to StripeStripe is a payment processing platform for online businesses.
Gridfox to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into inFakt
Pipedrive to inFaktPipedrive is a sales CRM and pipeline management tool.
HubSpot to inFaktHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to inFaktSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to inFaktSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to inFaktGoogle Sheets
Gmail to inFaktGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Questions
Gridfox and inFakt, answered
What can start an automation from Gridfox?
Any of Gridfox's 2 triggers in the catalog, including Record Created and Record Created or Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in inFakt when something happens in Gridfox?
Any of inFakt's 12 actions, including Create Client, Update Client, Update Product and Add Cost. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from inFakt to Gridfox?
inFakt has no triggers in the catalog today, so automations start in Gridfox. If you need the other direction, ask: your agent reads inFakt's API documentation and adds it.
Do I have to build a connector for Gridfox or inFakt?
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.