Integration
Connect Affinda to FacturaDirecta
When something happens in Affinda, your agent does the next thing in FacturaDirecta. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Affinda and FacturaDirecta to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Affinda and FacturaDirecta
Triggers and actions 2 triggers ยท 8 actions
Trigger
Document parsed (instant)Fires via a resthook subscription when Affinda finishes parsing a document.
- Add document
Upload a document (resume, invoice, job description, etc.) to Affinda for parsing.
- Delete document
Delete a document from Affinda.
- Find job descriptions by search expression
Search through parsed job descriptions matching given criteria.
- Get document
Retrieve a specific document and its parsed data by identifier.
- List documents
List all documents uploaded to Affinda.
- Search resumes
Search through parsed resumes matching given criteria.
Trigger
New ContactFires instantly when a contact is added in FacturaDirecta. Manual-registration webhook: in FacturaDirecta go to Settings then API and integrations then Webhooks, add a webhook endpoint subscribed specifically to the contact.created event, and paste this triggers minted URL as the endpoint. FacturaDirecta delivers only the events the endpoint is subscribed to, so the payload binds as {{ trigger.body.* }} (contact fields live under data.object, the event kind is in the type field such as contact.created).
- Create Client
Creates a client.
- Create Sales Invoice
Creates a sales invoice (with line-item support).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.