Connect Zamzar to Emailr

Both apps 23Zamzar 11Emailr 12

• Trigger
  New Conversion Job

  Triggered when a new conversion job is created in your Zamzar account.

• Trigger
  New File

  Triggered when a new file appears in your Zamzar account, whether uploaded or produced by a conversion.

• Action
  Convert File

  Starts a Zamzar conversion job that converts a file you supply into another format. Returns the new job with its id and status so you can check on it or collect the converted file later.

• Action
  Create Content File

  Creates a file on Zamzar from text content you supply, so it can be converted or downloaded later. Returns the stored file with its id, name and size.

• Action
  Delete conversion job

  Deletes a conversion job from Zamzar. Returns the job that was removed.

• Action
  Delete file

  Deletes a file stored on Zamzar. Returns the file that was removed.

• Action
  Find Converted File

  Looks through the files stored on Zamzar and returns the ones whose name matches the text you supply. Use it to locate a converted file after a conversion job has finished.

• Action
  Get conversion job

  Returns a single Zamzar conversion job, including its current status and any converted files it produced.

• Action
  Get file

  Returns the details of a single file stored on Zamzar, including its name, format and size.

• Action
  List conversion jobs

  Returns the conversion jobs in your Zamzar account, most recent first.

• Action
  List formats

  Returns every source format Zamzar can convert from, along with the target formats each one can be converted into.

• Action
  Add contact

  Create a contact. POST /v1/contacts

• Action
  Add segment

  Create a contact segment. POST /v1/segments

• Action
  Add template

  Create an email template. POST /v1/templates

• Action
  Delete contact

  Delete a contact by ID. DELETE /v1/contacts/{id}

• Action
  Delete segment

  Delete a segment by ID. DELETE /v1/segments/{id}

• Action
  Delete template

  Delete a template by ID. DELETE /v1/templates/{id}

• Action
  Get contact

  Fetch a contact by ID. GET /v1/contacts/{id}

• Action
  Get template

  Fetch a template by ID. GET /v1/templates/{id}

• Action
  List segments

  List contact segments. GET /v1/segments

• Action
  Update contact

  Update a contact by ID. PUT /v1/contacts/{id}

• Action
  Update segment

  Update a segment by ID. PUT /v1/segments/{id}

• Action
  Update template

  Update a template by ID. PUT /v1/templates/{id}

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