Connect Myphoner to Neon Postgres

Both apps 54Myphoner 25Neon Postgres 29

• Trigger
  Archived Lead

  Triggers when a lead is archived (marked 'archive').

• Trigger
  Call Back

  Triggers when a lead is marked for 'call back'.

• Trigger
  Lead updated (instant)

  Fires when a lead's information is updated by an agent (webhook event: lead_updated).

• Trigger
  Lost Lead

  Triggers when a lead is lost (marked 'loser').

• Trigger
  New call (instant)

  Fires when a new call is conducted (webhook event: new_call).

• Trigger
  New call recording (instant)

  Fires when a new call recording becomes available (webhook event: new_recording).

• Trigger
  New comment (instant)

  Fires when a new comment is created for a lead (webhook event: new_comment).

• Trigger
  New lead (instant)

  Fires when a new lead is created in Myphoner (webhook event: lead_created).

• Trigger
  New Winner

  Triggers when a lead is won.

• Trigger
  Text message received (instant)

  Fires when a text message is received from a lead (webhook event: inbound_text).

• Trigger
  Text message sent (instant)

  Fires when a text message is sent to a lead (webhook event: text).

• Action
  Archive a lead

  Archives a lead in Myphoner, optionally recording a comment and archive category, or scheduling the lead to come back for a call later.

• Action
  Create a list

  Creates a new lead list in Myphoner, optionally defining its columns.

• Action
  Create Lead

  Creates a lead in a Myphoner list. The lead's fields are the columns defined on the chosen list.

• Action
  Find Lead

  Searches Myphoner for a lead matching your text and returns the first match, optionally limited to certain lists.

• Action
  Get a lead

  Returns one Myphoner lead by its ID, including every column defined on the lead's list.

• Action
  Get a list

  Returns one Myphoner list by its ID, with its name, lead count and the categories configured for each lead state.

• Action
  List leads

  Returns a page of leads from a Myphoner list, newest-updated first when you ask for that order.

• Action
  List lists

  Returns every lead list in the Myphoner account, with each list's name, ID and lead count.

• Action
  Mark Lead as Loser

  Marks a Myphoner lead as lost, optionally recording a comment and loser category or scheduling it to come back for a call later.

• Action
  Mark Lead as Winner

  Marks a Myphoner lead as won, optionally recording a comment and winner category or scheduling it to come back for a call later.

• Action
  Mark Lead for Call Back

  Schedules a Myphoner lead for a call back, optionally recording a comment and category and setting when the lead should come back.

• Action
  Move a lead to another list

  Moves a Myphoner lead into a different list, optionally releasing it back to the calling queue.

• Action
  Search for Lead

  Searches Myphoner leads for your text and returns every match, optionally limited to certain lists.

• Action
  Update Lead

  Updates a lead in Myphoner. Only the fields you fill in are changed; the lead's fields are the columns defined on its list.

• Action
  Add branch

  Create a new branch in a Neon project.

• Action
  Add compute endpoint

  Creates a compute endpoint (a Neon compute instance) on a branch of a Neon project. A branch can have one read-write endpoint and multiple read-only endpoints.

• Action
  Add database

  Creates a new Postgres database in a Neon project branch, owned by an existing role.

• Action
  Add project

  Creates a new Neon Postgres project with its default branch, database, role and compute, and returns the project along with its connection details.

• Action
  Add role

  Creates a Postgres role in the specified Neon project branch. Connections to the branch's active compute are dropped while the change applies.

• Action
  Delete branch

  Delete a branch by project_id and branch_id.

• Action
  Delete compute endpoint

  Deletes a compute endpoint from a Neon project. Existing connections to the compute are dropped. If the compute does not exist or was already deleted, the step still succeeds with an empty result.

• Action
  Delete database

  Deletes the specified database from a branch of a Neon project.

• Action
  Delete project

  Deletes a Neon project and all its branches, compute endpoints, databases and roles. The project can be recovered within 7 days.

• Action
  Delete role

  Deletes the specified Postgres role from a Neon branch.

• Action
  Get branch

  Retrieves details of a branch in a Neon project.

• Action
  Get compute endpoint

  Retrieve details about a compute endpoint.

• Action
  Get connection URI

  Retrieve a Postgres connection URI for a database/role/branch/endpoint combination.

• Action
  Get database

  Retrieves details of a database on a Neon project branch.

• Action
  Get project

  Retrieves the details of a Neon project, including its settings, compute configuration, history retention, owner and current usage metrics.

• Action
  Get role

  Retrieves details about a Postgres role (user) on a Neon branch.

• Action
  Get role password

  Retrieves the password for a Postgres role on a Neon branch.

• Action
  List branches

  Retrieve a list of branches for a Neon project.

• Action
  List compute endpoints

  Lists the compute endpoints (Neon compute instances) in a project.

• Action
  List databases

  Lists the databases on a branch of a Neon project.

• Action
  List operations

  Lists the operations (asynchronous actions such as starting a compute or creating a branch) Neon performed on a project. Operations older than 6 months may no longer be available.

• Action
  List projects

  Lists the Neon projects accessible to the connected account, optionally filtered by name/ID or organization.

• Action
  List roles

  Lists the Postgres roles on a Neon project branch.

• Action
  Start compute endpoint

  Start (resume) a suspended compute endpoint.

• Action
  Suspend compute endpoint

  Suspends the specified Neon compute endpoint (scales it to zero).

• Action
  Update branch

  Update a branch's properties (e.g. name, protected) by project_id and branch_id.

• Action
  Update compute endpoint

  Updates an existing compute endpoint in a Neon project by ID.

• Action
  Update database

  Updates the name or owner of a database on a Neon project branch.

• Action
  Update project

  Update settings for a Neon project by project_id.

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