Connect Hellotracks to Signatureapi

Both apps 39Hellotracks 24Signatureapi 15

• Trigger
  Alert triggered

  Fires when a configured alert (late arrival, idle, zone entry/exit, low battery, etc.) triggers. Webhook key alert_triggered via /v1/webhooks or /api/setwebhooks (Hellotracks API).

• Trigger
  Completed Job

  Triggers when a job reaches a completed state.

• Trigger
  Member clocked in or out

  Fires when a worker turns location tracking on (clock-in) or off (clock-out) from the mobile app. Webhook key clock_in_out via /v1/webhooks or /api/setwebhooks (Hellotracks API).

• Trigger
  New Job

  Triggers when a job is created.

• Trigger
  Updated Job

  Triggers when a job is created, assigned, completed, archived, or otherwise updated.

• Action
  Add member

  Create a new team member (worker) account.

• Action
  Add place

  Create a new saved place/geofence.

• Action
  Archive Job

  Archives a job by ID.

• Action
  Auto-assign jobs

  Automatically assign a set of unassigned jobs to available members.

• Action
  Create Job

  Creates or updates a job. If External ID matches an existing job, the existing job is updated.

• Action
  Delete Job

  Deletes a job by ID.

• Action
  Delete member

  Delete a team member account.

• Action
  Distribute job

  Assign/distribute one or more jobs to members for dispatch.

• Action
  Find Job

  Finds a job by External ID.

• Action
  Find Member

  Finds a member by exact email, username, name, or UID.

• Action
  Generate report

  Generate a report (e.g. timesheet/activity) for a date range.

• Action
  Get company

  Get the authenticated company account's profile/settings.

• Action
  List places

  Get the company's saved places/geofences.

• Action
  Locate member

  Get a member's current/last known GPS location.

• Action
  Optimize route

  Compute an optimized route ordering for a member's assigned jobs.

• Action
  Restore job

  Restore a previously archived job.

• Action
  Update Job

  Updates a job by ID.

• Action
  Update member

  Edit an existing team member's fields.

• Action
  Update place

  Edit an existing saved place/geofence.

• Action
  Add ceremony

  Creates a new signing ceremony for a recipient. Any previous active ceremony for that recipient is revoked. Returns the ceremony, including its URL when the recipient is authenticated by email code or by your own application.

• Action
  Add deliverable

  Creates an additional deliverable (signed PDF package) from a completed envelope. The envelope must be completed.

• Action
  Add envelope

  Creates an envelope with documents and recipients and starts the signing process.

• Action
  Add upload

  Uploads a PDF, DOCX or PNG file to SignatureAPI and returns a URL you can use as a document source when creating an envelope. Uploads expire after 24 hours.

• Action
  Cancel envelope

  Cancel an in-progress envelope so remaining recipients can no longer sign.

• Action
  Delete envelope

  Delete an envelope.

• Action
  Get deliverable

  Retrieves a deliverable by its ID, including its status and, once generated, a download link for the signed PDF.

• Action
  Get envelope

  Retrieve a single envelope by id.

• Action
  Get recipient

  Retrieves a recipient's details, including status, ceremony information and completion timestamp.

• Action
  Get upload

  Fetches an uploaded file's record by ID: its format, size, hash and expiry. An error occurs if the upload is not found.

• Action
  List deliverables

  Returns the deliverables (signed PDFs with audit log) of an envelope, earliest first.

• Action
  List envelopes

  Lists envelopes in the account, most recent first, optionally filtered by status or topic.

• Action
  Resend request

  Resends the signing request to a recipient who has not yet completed their ceremony, e.g. as a reminder or after a lost or soft-bounced email.

• Action
  Update envelope

  Update mutable fields (e.g. title, metadata) of an existing envelope.

• Action
  Update recipient

  Replaces a recipient who has not yet completed with a new person. The original recipient is marked replaced and a new recipient is created with the same type, key, routing position and places.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.