Finnegans ERP

Description

The Finnegans nodes connect your workflows to the Finnegans GO / Teamplace ERP through its REST API. With them you can read, list, create, update and delete records of any entity in the ERP: providers, orders, invoices, products, receipts, payment orders, customers, etc.

There are five generic nodes, one per operation:

Node	Operation	HTTP method
Finnegans: Read entity (`finnegansGet`)	Read a record by its id/code	`GET /{Entity}/{id}`
Finnegans: List entity (`finnegansList`)	List/query with filters	`GET /{Entity}`
Finnegans: Create entity (`finnegansCreate`)	Create a record	`POST /{Entity}`
Finnegans: Update entity (`finnegansUpdate`)	Update a record	`PUT /{Entity}`
Finnegans: Delete entity (`finnegansDelete`)	Delete a record	`DELETE /{Entity}/{id}`

In all of them, Entity is the name of the resource in Finnegans (for example Proveedor, Pedido, Producto).

Credential

The nodes use a Finnegans ERP credential. Create it in Credentials → Add → Finnegans ERP with these fields:

Field	Description
API base URL	Your instance URL, no trailing slash. Default `https://api.teamplace.finneg.com/api` (some instances use a per-company subdomain).
Client ID	Generated in the ERP: Configuration → Security → Users → Keys api.
Client Secret	Generated together with the Client ID. Never shown in logs.
Environment	Production or Sandbox.

Authentication is OAuth2 (client_credentials): the nodes automatically obtain a token with your Client ID/Secret, reuse it while it’s valid (~1 hour) and renew it on their own when it expires. You don’t have to manage the token manually. In multi-server installations, the token is shared across servers to minimize authentication calls to the ERP.

Configuration

Common to all nodes

Parameter	Type	Required	Description
credentials_id	credentials	Yes	Finnegans credential
entity	text	Yes	Entity name (e.g. `Proveedor`, `Pedido`)

Per node

Read (finnegansGet): id (required) — id or code of the record. params (JSON, optional) — extra query parameters.
List (finnegansList): filters (JSON, optional) — query filters (pagination, fields, etc.).
Create (finnegansCreate): body (JSON, optional) — the record to create. If left empty, the node’s input data is used.
Update (finnegansUpdate): id (optional, depending on the entity) and body (JSON, optional; if empty, uses the input data).
Delete (finnegansDelete): id (required).

Convenience nodes (per-entity shortcuts)

Besides the five generic ones, there are shortcuts for the most-used entities: they come with the entity pre-set and clearly named fields, so you don’t have to remember the exact resource name.

Node	What it does	Equivalent to
Finnegans: Get provider (`finnegansGetProvider`)	Read a provider by its code	`finnegansGet` with entity `Proveedor`
Finnegans: Get product (`finnegansGetProduct`)	Read a product by its code	`finnegansGet` with entity `Producto`
Finnegans: Create order (`finnegansCreateOrder`)	Create an order	`finnegansCreate` with entity `Pedido`
Finnegans: Create invoice (`finnegansCreateInvoice`)	Create an invoice/voucher	`finnegansCreate` with entity `Comprobante`

For the create nodes, the body comes from the matching field (Order / Invoice, as JSON) or, if left empty, from the node’s input data. If your instance names the resource differently (e.g. PedidoVenta or Factura), you can override the name in the node’s Entity field.

Example

Read the provider with code 4249:

Node: Finnegans: Read entity
entity: Proveedor
id: 4249

Output (the entity data as returned by Finnegans):

{
  "Nombre": "EMPRESA PROVINCIAL DE ENERGIA DE CORDOBA",
  "Codigo": "4249",
  "Activo": true,
  "IdentificacionTributariaNumero": "30-99902748-9"
}

Error handling

Each node classifies errors so the engine knows whether retrying makes sense:

Situation	Retryable	What to do
Validation (400/422)	No	Finnegans returns the reason (e.g. “Falta especificar la organización”). Fix the input data.
Not found (404)	No	The entity or id doesn’t exist. Check the entity name and id.
Authentication (401/403)	No	Invalid Client ID/Secret or no permission. Check the credential.
Server (500)	Yes	Temporary ERP error; retried automatically.
Network / Timeout / Limit (429)	Yes	Transient issue; retried automatically.

Finnegans’ error message is propagated as-is to the workflow, so you can see it in the execution trace.