Overview
Connect FreeAgent with Flows360
Accounting and invoicing software for small businesses
Use the FreeAgent connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and 4 triggers.
Available actions
- Create Task
- Create Contact
Available triggers
- New Invoice
- New Contact
- New User
- New Task
The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.
Technical guide
Technical reference
Package identity
- Connector: FreeAgent
- Package:
@activepieces/piece-free-agent@0.1.7 - Exact artifact digest:
sha256:2b3a0b3e634ba3d89fb1376ccbec895b7c4ed495e2d93ecdf3a131bfa5737f86 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Create Task (
create_task), Create a task inside a project Classification: read. - Create Contact (
create_contact), Create a new contact in FreeAgent Classification: read.
Trigger contracts
- New Invoice, polling.
- New Contact, polling.
- New User, polling.
- New Task, polling.
Verification
Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Capability summary
Authentication
Authentication method: OAuth 2.0
Authentication profiles
connection · oauth2
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Create Task | Yes | No | Create a task inside a project |
| Create Contact | Yes | No | Create a new contact in FreeAgent |
| New Invoice | Yes | No | polling trigger declared by the pinned package. |
| New Contact | Yes | No | polling trigger declared by the pinned package. |
| New User | Yes | No | polling trigger declared by the pinned package. |
| New Task | Yes | No | polling trigger declared by the pinned package. |
Supported actions
Create Task · Read
Create a task inside a project
create_task · Risk: low · Retry: safe
Inputs
project_id· string · Required, Select the project to create the task inname· string · Required, The name of the taskis_billable· boolean · Optional, Whether this task is billable to clientsbilling_rate· number · Optional, The rate at which the project is billed per billing periodbilling_period· string · Optional, The period for billing ratestatus· string · Optional, The status of the task
Create Contact · Read
Create a new contact in FreeAgent
create_contact · Risk: low · Retry: safe
Inputs
first_name· string · Optional, First name (required if organization name is not specified)last_name· string · Optional, Last name (required if organization name is not specified)organisation_name· string · Optional, Organization name (required if first and last name are not specified)email· string · Optional, Email addressbilling_email· string · Optional, Billing email addressphone_number· string · Optional, Telephone numbermobile· string · Optional, Mobile numberaddress1· string · Optional, First line of the addressaddress2· string · Optional, Second line of the addressaddress3· string · Optional, Third line of the addresstown· string · Optional, Town or cityregion· string · Optional, Region or statepostcode· string · Optional, Post or ZIP codecountry· string · Optional, Countrycontact_name_on_invoices· boolean · Optional, Show contact name as well as organization name on invoicesdefault_payment_terms_in_days· number · Optional, Default payment terms in dayscharge_sales_tax· string · Optional, How to handle sales tax for this contactsales_tax_registration_number· string · Optional, Sales tax registration number if applicablestatus· string · Optional, Contact statuslocale· string · Optional, Invoice/estimate language
Triggers
New Invoice · Poll
Triggers when a new invoice is created
Inputs
status· stringinclude_items· boolean
New Contact · Poll
Triggers when a new contact is created
Inputs
status· string
New User · Poll
Triggers when a new user is added
Inputs
view· string
New Task · Poll
Triggers when a new task is added
Inputs
status· string
Setup
Setup
- Add the FreeAgent connector to the workflow in the target Flows360 Studio instance.
- Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
- Provide the connection fields declared by the pinned package:
- No provider credential fields are declared by the pinned package.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-free-agent@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 2 actions and 4 triggers declared by this pinned package are represented here.
- Tenant credentials and connection values are not stored in the public connector record.
- Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
- Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required FreeAgent connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.
Why is an action or trigger unavailable?
Confirm that the workflow is using @activepieces/piece-free-agent@0.1.7 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.
What should I check after a provider-side change?
Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.