Overview
Connect iLoveAPI with Flows360
Compress, merge, split, convert, OCR, watermark, protect and sign PDFs and images using iLovePDF / iLoveIMG / iLoveSign.
Use the iLoveAPI 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 22 actions and 11 triggers.
Available actions
- Compress PDF
- Merge PDF
- Split PDF
- PDF to JPG
- JPG to PDF
- Office to PDF
- HTML to PDF
- OCR PDF
- Plus 14 additional declared actions.
Available triggers
- Task Completed
- Task Failed
- Signature Created
- Signature Sent
- Signature Completed
- Signature Declined
- Plus 5 additional declared triggers.
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: iLoveAPI
- Package:
@activepieces/piece-iloveapi@0.0.6 - Exact artifact digest:
sha256:6b990389ac0b5d2b165753c8d55d180c0d0d25aaf2ba6764ca20b168ce2bf4ba - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Compress PDF (
compress_pdf), Reduce the size of a PDF file using iLoveAPI. Classification: read. - Merge PDF (
merge_pdf), Combine multiple PDF files into a single document, in the order provided. Classification: read. - Split PDF (
split_pdf), Split a PDF by page ranges, fixed page batches, removed pages, or target file size. Classification: read. - PDF to JPG (
pdf_to_jpg), Convert PDF pages to JPG images, or extract images embedded in the PDF. Classification: read. - JPG to PDF (
jpg_to_pdf), Convert one or more images (JPG/PNG) into a PDF document. Classification: read. - Office to PDF (
office_to_pdf), Convert Office documents (DOCX, XLSX, PPTX, ODT, etc.) to PDF. Classification: read. - HTML to PDF (
html_to_pdf), Convert a publicly accessible web page URL into a PDF. Classification: read. - OCR PDF (
ocr_pdf), Run OCR on a PDF to make scanned documents searchable. Supports 100+ languages. Classification: read. - Watermark PDF (
watermark_pdf), Stamp a text or image watermark across pages of a PDF. Classification: read. - Protect PDF (
protect_pdf), Add a password to a PDF document. Classification: read. - Unlock PDF (
unlock_pdf), Remove the password from a PDF (you must know the current password). Classification: read. - Add Page Numbers to PDF (
page_numbers_pdf), Stamp page numbers onto a PDF, with control over position and styling. Classification: read. - Rotate PDF (
rotate_pdf), Rotate every page of a PDF by 90, 180, or 270 degrees. Classification: read. - Extract Text from PDF (
extract_text_pdf), Extract plain or detailed text (with positions and font metadata) from a PDF. Classification: read. - Repair PDF (
repair_pdf), Attempt to fix a damaged or corrupted PDF file. Classification: read. - Create Signature Request (
create_signature_request), Send one or more PDF documents for electronic signature, with custom signers and signature placeholders. Classification: read. - Get Signature Status (
get_signature_status), Look up the current status of a signature request, including each signer. Classification: read. - Send Signer Reminder (
send_signer_reminder), Email a reminder to signers who have not yet completed the signature. Limited to 2 calls per day. Classification: read. - Void Signature (
void_signature), Cancel an in-progress signature request. The document becomes inaccessible to all signers. Classification: read. - Increase Expiration Days (
increase_expiration_days), Extend the expiration of a signature request by a number of days. Total cannot exceed 130 days from now. Classification: read. - Download Signed Files (
download_signed_files), Download the signed PDF (or ZIP if multiple files). The signature must be in "completed" status. Classification: read. - Download Audit Trail (
download_audit_trail), Download the audit-trail PDF for a completed signature request. Useful for compliance and dispute resolution. Classification: read.
Trigger contracts
- Task Completed, webhook.
- Task Failed, webhook.
- Signature Created, webhook.
- Signature Sent, webhook.
- Signature Completed, webhook.
- Signature Declined, webhook.
- Signature Expired, webhook.
- Signature Voided, webhook.
- Signer Viewed Document, webhook.
- Signer Signed, webhook.
- Signer Declined, webhook.
Verification
Runtime execution evidence is managed separately from package metadata.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- Project Public Key Required · protected credential
Triggers
Task Completed · Webhook
Fires when a processing task finishes successfully. Optionally filter by tool.
Inputs
instructions· stringtools· array
Task Failed · Webhook
Fires when a processing task fails. Optionally filter by tool.
Inputs
instructions· stringtools· array
Signature Created · Webhook
Fires when a new signature request is created.
Inputs
instructions· string
Signature Sent · Webhook
Fires when a signature request is sent to all receivers.
Inputs
instructions· string
Signature Completed · Webhook
Fires when every signer has finished. Use this to drive contract-completion automations.
Inputs
instructions· string
Signature Declined · Webhook
Fires when a signer or validator declines the signature request.
Inputs
instructions· string
Signature Expired · Webhook
Fires when a signature request reaches its expiration date.
Inputs
instructions· string
Signature Voided · Webhook
Fires when the requester cancels an in-progress signature.
Inputs
instructions· string
Signer Viewed Document · Webhook
Fires when an individual receiver opens the document.
Inputs
instructions· string
Signer Signed · Webhook
Fires when an individual signer completes their signature.
Inputs
instructions· string
Signer Declined · Webhook
Fires when an individual signer declines to sign.
Inputs
instructions· string
Setup
Setup
- Add the iLoveAPI 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-iloveapi@0.0.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 22 actions and 11 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.
- Runtime execution evidence is managed separately from package metadata.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required iLoveAPI 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-iloveapi@0.0.6 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.