Log inStart trial

Affinda and Keeping Integration

Demonstration of how apps are integrated in WEXTL workflow builder [4]

Keep Affinda and Keeping in sync by integrating their events and actions. When hr events happen in Affinda, update the Keeping automatically - without any line of code in visual workflow builder.

Integration guide
  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Affinda and Keeping

Detailed info you need to know about Affinda and Keeping integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Affinda

    • HR
    • 2 triggers
    • 3 searches
    • 2 actions

    AI document parsing for resumes, invoices, and structured data extraction. [5]

  • Keeping

    • HR
    • 6 triggers
    • 12 searches
    • 19 actions

    Time tracking software for logging hours against clients, projects and tasks. [6]

How to connect Affinda to Keeping

Set up your Affinda and Keeping integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.

  1. STEP 1

    Connect Affinda and Keeping

    Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.

  2. STEP 2

    Build a workflow

    Paste selected Affinda and Keeping nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.

  3. STEP 3

    Map your data

    Choose which fields need to sync between Affinda and Keeping. Use filters or leverage a JS custom code step in between — everything is on the canvas.

How does the integration between Affinda and Keeping work in WEXTL?

WEXTL exposes actions and triggers for Affinda and Keeping that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.

Affinda triggersKeeping actions

Affinda modules

  • Get a Document Retrieves a single document.
  • Get a Redacted Document Retrieves a redacted version of a document.
  • Make an API Call Performs an arbitrary authorized API call.
  • Search Documents Searches for documents.
  • Upload a Document Uploads a document for parsing.
  • Watch Documents Triggers when a document is created.
  • Watch Events Triggers when a specified event occurs.

Keeping modules

  • Archive a Project Sets a project's state to archived.
  • Archive a Task Sets a task's state to archived.
  • Create a Client Creates a new client.
  • Create a Project Creates a new project.
  • Create a Task Creates a new task.
  • Create an Entry Creates a new time entry.
  • Delete a Client Permanently deletes a client.
  • Delete a Project Permanently deletes a project.
  • Delete a Task Permanently deletes a task.
  • Delete an Entry Permanently deletes a time entry.
  • Get a Client Retrieves a client by ID.
  • Get a Project Retrieves a project by ID.
  • Get a Task Retrieves a task by ID.
  • Get a User Retrieves a single user of the organisation.
  • Get an Entry Retrieves a single time entry.
  • Get Current User Retrieves the organisation user that belongs to the connection in use.
  • List Clients Lists the clients in the organisation.
  • List Organizations Lists all your currently active organisations.
  • List Projects Lists the projects in the organisation.
  • List Tasks Lists the tasks in the organisation.
  • List Timesheet Entries Lists time entries in the organisation.
  • List Users Lists the users in the organisation.
  • Make an API Call Sends a custom authorized request to the Keeping API.
  • Restore a Project Sets an archived project's state back to active.
  • Restore a Task Sets an archived task's state back to active.
  • Resume an Entry Resumes a stopped time entry.
  • Stop an Entry Stops a running time entry.
  • Update a Client Updates a client by ID.
  • Update a Project Updates a project by ID.
  • Update a Task Updates an existing task.
  • Update an Entry Modifies an existing time entry.
  • Watch Clients Triggers when a new client is added to an organisation.
  • Watch Organizations Triggers when a new organisation becomes available.
  • Watch Projects Triggers when a new project is added to an organisation.
  • Watch Tasks Triggers when a new task is added to an organisation.
  • Watch Timesheet Entries Triggers when a new time entry is added to an organisation.
  • Watch Users Triggers when a new user is added to an organisation.

Explore alternative integrations

There are other apps [9] supported by WEXTL that can be paired with Affinda and Keeping integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Affinda and Keeping on WEXTL®

Claim your 3-day trial to build Affinda with Keeping integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Affinda and Keeping.

How do I connect Affinda and Keeping?

Connect your Affinda and Keeping accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]

What can I automate between Affinda and Keeping?

Example: when Affinda's "Watch Documents" fires, WEXTL can "Archive a Project" in Keeping. Affinda has 2 triggers (including Watch Documents and Watch Events); Keeping has 31 actions (including Archive a Project, Archive a Task, and Create a Client). Add filters and transforms between steps when you need them. [1]

Can Affinda trigger actions in Keeping, and Keeping in Affinda?

Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]

Do I need to write code to integrate Affinda and Keeping?

No. Affinda-to-Keeping automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]

Does Affinda integrate with Keeping in real time?

Yes. Trigger-based automations start the moment Affinda (or Keeping) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]

How long does it take to set up a Affinda + Keeping integration?

A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Affinda with Keeping?

You can build your Affinda + Keeping automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]

References

List of sources used to gather information about the Affinda and Keeping integration.

  1. Affinda and Keeping integration source code, module specs and credentials implementation.
  2. Our Affinda and Keeping integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Affinda and Keeping — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Affinda integration information
  6. Keeping integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Affinda and Keeping integration page documentation. Used sources, AI's role, and how the team validates the result.

Explore Affinda and Keeping, or get started