Data source: pipefy_email_templates

[Danielmoraisg]

Summary

Automations that send email reference a template id, and today there is no way to look one up from Terraform, so configs hardcode ids. The API reads templates per repo (emailTemplates on a pipe or table, with name filtering and pagination).

Proposed schema

• Inputs: repo_id (required: pipe or table id), name (optional filter)
• Outputs: list of templates with id, name, subject, and the addressing fields the query exposes

Notes

• Templates can contain long HTML bodies; the data source only needs the fields used for referencing and disambiguation, not the full body.
• The query is paginated; this needs cursor handling in the client (internal/provider/client/api_client.go), same as the list queries in Data sources: pipefy_organization, pipe lookup by name, phase fields #49.